Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84d497be490ab2a5ec038df4b5c73adb6530a609259336f3a79e12bde01d4795

Tx prefix hash: c568993c0048207b01da860cf2ed129b657f33a29e01200a928f1c02f3ff4a80
Tx public key: 0a479e87366a8f2b320eb0e728ab2531cd90d4f89c2f839c0e0fda3246cb535a
Timestamp: 1743689511 Timestamp [UCT]: 2025-04-03 14:11:51 Age [y:d:h:m:s]: 00:225:10:51:05
Block: 1253456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158863 RingCT/type: yes/0
Extra: 010a479e87366a8f2b320eb0e728ab2531cd90d4f89c2f839c0e0fda3246cb535a021100000005a2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d425345109a99bc6996b7ab3a0a19510faf3f6f621ffae75ff254af033a701b 0.600000000000 1740537 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": 1253466, "vin": [ { "gen": { "height": 1253456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d425345109a99bc6996b7ab3a0a19510faf3f6f621ffae75ff254af033a701b" } } ], "extra": [ 1, 10, 71, 158, 135, 54, 106, 143, 43, 50, 14, 176, 231, 40, 171, 37, 49, 205, 144, 212, 248, 156, 47, 131, 156, 14, 15, 218, 50, 70, 203, 83, 90, 2, 17, 0, 0, 0, 5, 162, 237, 1, 107, 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