Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16222a976273ea2b9453c42ee2124b746e34033376c096dcab0edf1093cad391

Tx prefix hash: 02e60bbcde1a35cbe6ed4c8728829180f2983aaa34f9a9afd831440ec0424760
Tx public key: 880f31fd34d03b607c76d7dfc9c6d8f6fc10fb0f47684a5f3f098b54cce18d5e
Timestamp: 1681420722 Timestamp [UCT]: 2023-04-13 21:18:42 Age [y:d:h:m:s]: 02:209:16:44:43
Block: 737952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 669742 RingCT/type: yes/0
Extra: 01880f31fd34d03b607c76d7dfc9c6d8f6fc10fb0f47684a5f3f098b54cce18d5e0211000000035029cbac000000000000000000

1 output(s) for total of 2.202210892000 dcy

stealth address amount amount idx
00: 568cec0dd56112c0e80f40388e1f1b2692fa7a004ef5f709e2d4ac424227936e 2.202210892000 1184581 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": 737962, "vin": [ { "gen": { "height": 737952 } } ], "vout": [ { "amount": 2202210892, "target": { "key": "568cec0dd56112c0e80f40388e1f1b2692fa7a004ef5f709e2d4ac424227936e" } } ], "extra": [ 1, 136, 15, 49, 253, 52, 208, 59, 96, 124, 118, 215, 223, 201, 198, 216, 246, 252, 16, 251, 15, 71, 104, 74, 95, 63, 9, 139, 84, 204, 225, 141, 94, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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