Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ad3ba731559ac4d8fa00210348d29fdb819cfdc7d58aaefb38825c905e17f3f

Tx prefix hash: c51bcfa41c5918e9330c8fea4c6307ca40441cace63c510cc4ba41d8d42de085
Tx public key: 606437e83a6af2e2d2b8e2d37f2ee1de3494b3e11297e896fe09e9e821f23dee
Timestamp: 1609982908 Timestamp [UCT]: 2021-01-07 01:28:28 Age [y:d:h:m:s]: 04:032:06:23:26
Block: 175539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1038400 RingCT/type: yes/0
Extra: 01606437e83a6af2e2d2b8e2d37f2ee1de3494b3e11297e896fe09e9e821f23dee021100000016f6643c68000000000000000000

1 output(s) for total of 160.838347044000 dcy

stealth address amount amount idx
00: 05663b9e2be57c91c198b35f377d876257df9f44e0cf3b32e83aea1ccef20948 160.838347044000 335345 of 0

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": 175549, "vin": [ { "gen": { "height": 175539 } } ], "vout": [ { "amount": 160838347044, "target": { "key": "05663b9e2be57c91c198b35f377d876257df9f44e0cf3b32e83aea1ccef20948" } } ], "extra": [ 1, 96, 100, 55, 232, 58, 106, 242, 226, 210, 184, 226, 211, 127, 46, 225, 222, 52, 148, 179, 225, 18, 151, 232, 150, 254, 9, 233, 232, 33, 242, 61, 238, 2, 17, 0, 0, 0, 22, 246, 100, 60, 104, 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