Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa8d9c763f41c68678e11b95b75c8a1140275ea3ee367e4a93ffb0f046fa4efb

Tx prefix hash: 9622c8c0b1844e7af4d4a8d689eddfeacc5cb9aeffadcf8f8834d249c63ce718
Tx public key: bef0d2635d21b7690c7facc3e98965949531363ae59e89400d68dac33f4bb786
Timestamp: 1702410439 Timestamp [UCT]: 2023-12-12 19:47:19 Age [y:d:h:m:s]: 02:015:03:47:06
Block: 911743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530613 RingCT/type: yes/0
Extra: 01bef0d2635d21b7690c7facc3e98965949531363ae59e89400d68dac33f4bb78602110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9280598cb4c5447c75a125c73fbe7e1c9c0fd96468524bf45b18bce772543572 0.600000000000 1368959 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": 911753, "vin": [ { "gen": { "height": 911743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9280598cb4c5447c75a125c73fbe7e1c9c0fd96468524bf45b18bce772543572" } } ], "extra": [ 1, 190, 240, 210, 99, 93, 33, 183, 105, 12, 127, 172, 195, 233, 137, 101, 148, 149, 49, 54, 58, 229, 158, 137, 64, 13, 104, 218, 195, 63, 75, 183, 134, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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