Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3109f168fb097ee10f6f100726c929ff38ae3496fb742026906a125e038ed28d

Tx prefix hash: bd50efe976d6c305192e42669cd1cfb4fa56ae697902754e4c291f13953f1cab
Tx public key: a01b629f341d8f66ad39c5f68f1d0c082a31e36af7332582b41b24966057f8e6
Timestamp: 1681745722 Timestamp [UCT]: 2023-04-17 15:35:22 Age [y:d:h:m:s]: 02:200:12:20:56
Block: 740650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 663155 RingCT/type: yes/0
Extra: 01a01b629f341d8f66ad39c5f68f1d0c082a31e36af7332582b41b24966057f8e602110000000175e3f0e9000000000000000000

1 output(s) for total of 2.157343539000 dcy

stealth address amount amount idx
00: 5dbd3d1eca23dac37ba20f7541407556cb1c02a8b46c0477bd0e27cb3e6c3be0 2.157343539000 1187549 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": 740660, "vin": [ { "gen": { "height": 740650 } } ], "vout": [ { "amount": 2157343539, "target": { "key": "5dbd3d1eca23dac37ba20f7541407556cb1c02a8b46c0477bd0e27cb3e6c3be0" } } ], "extra": [ 1, 160, 27, 98, 159, 52, 29, 143, 102, 173, 57, 197, 246, 143, 29, 12, 8, 42, 49, 227, 106, 247, 51, 37, 130, 180, 27, 36, 150, 96, 87, 248, 230, 2, 17, 0, 0, 0, 1, 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