Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 321d11c46bd034580c94fdca0e1ed6089e953f121d0aef6946b1a0b68f12afff

Tx prefix hash: eee262e2a4d62f43879d6a6001e5f064a5437a1b4f0440a7a0b64a1756a8d27f
Tx public key: d4e8e458ff569e5cad1bc02d5484ff2b6260602af7763221f059ba8f8ccd4e37
Timestamp: 1717146758 Timestamp [UCT]: 2024-05-31 09:12:38 Age [y:d:h:m:s]: 01:221:20:22:36
Block: 1033906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417219 RingCT/type: yes/0
Extra: 01d4e8e458ff569e5cad1bc02d5484ff2b6260602af7763221f059ba8f8ccd4e3702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d06e94155576624101b1667dc07548ba34fc511cd2c7027c747408034afcd7ab 0.600000000000 1502379 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": 1033916, "vin": [ { "gen": { "height": 1033906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d06e94155576624101b1667dc07548ba34fc511cd2c7027c747408034afcd7ab" } } ], "extra": [ 1, 212, 232, 228, 88, 255, 86, 158, 92, 173, 27, 192, 45, 84, 132, 255, 43, 98, 96, 96, 42, 247, 118, 50, 33, 240, 89, 186, 143, 140, 205, 78, 55, 2, 17, 0, 0, 0, 3, 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