Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf5036102673dcc652ec67441d491694eee6dcb633fb3ad2e265f1d6dce18892

Tx prefix hash: 081470e821e8a9529d742986fae4cca8385f296e796d0fd2aa9e1d68b26f775d
Tx public key: f9458cf2f17d80234a3e311ef17bbb674f4aeecd0accac4dd3de475596cf5508
Timestamp: 1736026372 Timestamp [UCT]: 2025-01-04 21:32:52 Age [y:d:h:m:s]: 00:103:11:56:14
Block: 1190293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73758 RingCT/type: yes/0
Extra: 01f9458cf2f17d80234a3e311ef17bbb674f4aeecd0accac4dd3de475596cf550802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 606831c8c867f58d537e7e1df7cb1c9829153daf23584103b11aea47993e0194 0.600000000000 1676808 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": 1190303, "vin": [ { "gen": { "height": 1190293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "606831c8c867f58d537e7e1df7cb1c9829153daf23584103b11aea47993e0194" } } ], "extra": [ 1, 249, 69, 140, 242, 241, 125, 128, 35, 74, 62, 49, 30, 241, 123, 187, 103, 79, 74, 238, 205, 10, 204, 172, 77, 211, 222, 71, 85, 150, 207, 85, 8, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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