Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96802e6d97291793162009f46c025323da14bbe1dc22d00064fb004f50d1c691

Tx prefix hash: dd47099d114c263565b2cfcfb53801f79268addd6b0c5e13e1b6e999aca117e2
Tx public key: 52e1b0d284c867f86199bc6348d1b397cfae904cc012e286a0d8a62e52fad207
Timestamp: 1749821457 Timestamp [UCT]: 2025-06-13 13:30:57 Age [y:d:h:m:s]: 00:149:14:41:16
Block: 1304160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104675 RingCT/type: yes/0
Extra: 0152e1b0d284c867f86199bc6348d1b397cfae904cc012e286a0d8a62e52fad207021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64dffcb4d83334a063d0484c67960ea072a475600e4bf3ad3df42ffeb6c79d93 0.600000000000 1791747 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": 1304170, "vin": [ { "gen": { "height": 1304160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64dffcb4d83334a063d0484c67960ea072a475600e4bf3ad3df42ffeb6c79d93" } } ], "extra": [ 1, 82, 225, 176, 210, 132, 200, 103, 248, 97, 153, 188, 99, 72, 209, 179, 151, 207, 174, 144, 76, 192, 18, 226, 134, 160, 216, 166, 46, 82, 250, 210, 7, 2, 17, 0, 0, 0, 1, 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