Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dd71fa7f0ec4cd4fa32463dc59d8066647f1e75988f24ef300bfba6f5c3aaac

Tx prefix hash: 013f11b0b7a4932c4bda6fda9341c13e85cc85db6bd2ae41809289e82f9dbbf6
Tx public key: ca42523cdc848c5dd693dcd36a0ffdbaec51b2ca0a0e2b90207ebb30a0d0a9fe
Timestamp: 1752810976 Timestamp [UCT]: 2025-07-18 03:56:16 Age [y:d:h:m:s]: 00:165:00:51:12
Block: 1327861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116783 RingCT/type: yes/0
Extra: 01ca42523cdc848c5dd693dcd36a0ffdbaec51b2ca0a0e2b90207ebb30a0d0a9fe021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07e47c609727947e21c46173bf2246e3a80800c675061ed3fcd5c3461fcca962 0.600000000000 1815620 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": 1327871, "vin": [ { "gen": { "height": 1327861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07e47c609727947e21c46173bf2246e3a80800c675061ed3fcd5c3461fcca962" } } ], "extra": [ 1, 202, 66, 82, 60, 220, 132, 140, 93, 214, 147, 220, 211, 106, 15, 253, 186, 236, 81, 178, 202, 10, 14, 43, 144, 32, 126, 187, 48, 160, 208, 169, 254, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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