Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2eccf34d71cc71ac46879c92d1ce9f4bd53ba5472984cb901ef55b03a9e833a2

Tx prefix hash: 139c34ae877a924289b1521401d50ebb8b230530b80b2f90f88b174b7e3b665d
Tx public key: e705a47f85b7125bf5e52cbbb55ee8cd3c500f07db7e0c2b757ccbfe8c4a0b99
Timestamp: 1715983804 Timestamp [UCT]: 2024-05-17 22:10:04 Age [y:d:h:m:s]: 00:347:20:49:57
Block: 1024259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248649 RingCT/type: yes/0
Extra: 01e705a47f85b7125bf5e52cbbb55ee8cd3c500f07db7e0c2b757ccbfe8c4a0b9902110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba984a7e1df676a301ec95fea395ee62b9e4a026b35edbf50df69f2086d22006 0.600000000000 1489864 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": 1024269, "vin": [ { "gen": { "height": 1024259 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba984a7e1df676a301ec95fea395ee62b9e4a026b35edbf50df69f2086d22006" } } ], "extra": [ 1, 231, 5, 164, 127, 133, 183, 18, 91, 245, 229, 44, 187, 181, 94, 232, 205, 60, 80, 15, 7, 219, 126, 12, 43, 117, 124, 203, 254, 140, 74, 11, 153, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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