Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b1120131f5d45964a887f604afb398cd08fe8b71abe0e540753b584400865137

Tx prefix hash: bee4a4e1ca09c25ec1c9e91c2f5dd4944caed0955f7eb35d589fe41af80ac18d
Tx public key: 0a6bbeecb0d3dcd700ef1cbb9e1c7a64879f1e9c6b06fd32ab65592cdb7fbb2f
Timestamp: 1720187867 Timestamp [UCT]: 2024-07-05 13:57:47 Age [y:d:h:m:s]: 01:126:15:53:22
Block: 1059106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349060 RingCT/type: yes/0
Extra: 010a6bbeecb0d3dcd700ef1cbb9e1c7a64879f1e9c6b06fd32ab65592cdb7fbb2f0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bf69234957f07af245cb7f707825fe7475781332301512d2f0e9ff30fb4648c 0.600000000000 1529567 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1059116, "vin": [ { "gen": { "height": 1059106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bf69234957f07af245cb7f707825fe7475781332301512d2f0e9ff30fb4648c" } } ], "extra": [ 1, 10, 107, 190, 236, 176, 211, 220, 215, 0, 239, 28, 187, 158, 28, 122, 100, 135, 159, 30, 156, 107, 6, 253, 50, 171, 101, 89, 44, 219, 127, 187, 47, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8