Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e703bbbaba57ded3f821bedbcbf820bdd9a1fee8ec6d769c1086eb9803d079c

Tx prefix hash: 9781f9b681a8822a94a0c35653677d488b70194aeccf6d342f57ba5ca1286d33
Tx public key: 82e9f9dcbb32840ff5451366a3be6406c08ae771c85041012febd64dbbdd8a2a
Timestamp: 1715419813 Timestamp [UCT]: 2024-05-11 09:30:13 Age [y:d:h:m:s]: 00:327:14:36:00
Block: 1019616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234145 RingCT/type: yes/0
Extra: 0182e9f9dcbb32840ff5451366a3be6406c08ae771c85041012febd64dbbdd8a2a02110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2eb34a518632c51f05d2c2f715d0903f7e48e906c55ede215e93e9e1856c603 0.600000000000 1483637 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": 1019626, "vin": [ { "gen": { "height": 1019616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2eb34a518632c51f05d2c2f715d0903f7e48e906c55ede215e93e9e1856c603" } } ], "extra": [ 1, 130, 233, 249, 220, 187, 50, 132, 15, 245, 69, 19, 102, 163, 190, 100, 6, 192, 138, 231, 113, 200, 80, 65, 1, 47, 235, 214, 77, 187, 221, 138, 42, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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