Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8aada48592b7147f426d3266317dac6f2c844f8facf48724e8854beca7f10f06

Tx prefix hash: d36529df4026920b594b7463301594fd61a6a769cc8917a6056c1188cadc1765
Tx public key: 2c4a2bb8395eab1aa0d20c1f17b3dc585f7778005cf21ddfc8e1090a5e956bd4
Timestamp: 1736263246 Timestamp [UCT]: 2025-01-07 15:20:46 Age [y:d:h:m:s]: 00:086:10:18:37
Block: 1192257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61536 RingCT/type: yes/0
Extra: 012c4a2bb8395eab1aa0d20c1f17b3dc585f7778005cf21ddfc8e1090a5e956bd4021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2aab820ea419c1877872b853fae303e6ae918d89f74ce46975a408758fe1226f 0.600000000000 1678806 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": 1192267, "vin": [ { "gen": { "height": 1192257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2aab820ea419c1877872b853fae303e6ae918d89f74ce46975a408758fe1226f" } } ], "extra": [ 1, 44, 74, 43, 184, 57, 94, 171, 26, 160, 210, 12, 31, 23, 179, 220, 88, 95, 119, 120, 0, 92, 242, 29, 223, 200, 225, 9, 10, 94, 149, 107, 212, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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