Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c37d209f9772071a6c7ce1ae75328036ce357a9b6dc99a86efbf8c2d4bf7d97

Tx prefix hash: 63e8f8473148f43d0dff497cbb4deaf7286d88db1b3a1bb81ce1adcd5adfd26d
Tx public key: a385a0181df584e981ba764d876b634bd2827f5a3164d5be31e5ab866e9f1f01
Timestamp: 1719146554 Timestamp [UCT]: 2024-06-23 12:42:34 Age [y:d:h:m:s]: 00:308:09:09:40
Block: 1050460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220401 RingCT/type: yes/0
Extra: 01a385a0181df584e981ba764d876b634bd2827f5a3164d5be31e5ab866e9f1f0102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67af1b2b76479b49121b5ef96fd7f78868395496f941090a16cc4c7ea94a9939 0.600000000000 1520633 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": 1050470, "vin": [ { "gen": { "height": 1050460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67af1b2b76479b49121b5ef96fd7f78868395496f941090a16cc4c7ea94a9939" } } ], "extra": [ 1, 163, 133, 160, 24, 29, 245, 132, 233, 129, 186, 118, 77, 135, 107, 99, 75, 210, 130, 127, 90, 49, 100, 213, 190, 49, 229, 171, 134, 110, 159, 31, 1, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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