Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c29845d09c0c9e58562423d0eee352f91df5acae6538e2b4ebd0db6ae12b08b

Tx prefix hash: 227ce4ddfae94909571bf34e2119c70e5e7dd4f4fcd4526a2c9be5c7de6596b2
Tx public key: 111b40f598c1d61ca02e0a8a041174c7e4ed88d6ca9a438fa6c9736095a21623
Timestamp: 1583080319 Timestamp [UCT]: 2020-03-01 16:31:59 Age [y:d:h:m:s]: 05:071:07:38:36
Block: 74609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1205609 RingCT/type: yes/0
Extra: 01111b40f598c1d61ca02e0a8a041174c7e4ed88d6ca9a438fa6c9736095a2162302110000017f56c366d3000000000000000000

1 output(s) for total of 347.368320742000 dcy

stealth address amount amount idx
00: 01b7e530d0b576a362fdb4b1538393413e8d187458a98633de816e4fb968e6cc 347.368320742000 138035 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": 74619, "vin": [ { "gen": { "height": 74609 } } ], "vout": [ { "amount": 347368320742, "target": { "key": "01b7e530d0b576a362fdb4b1538393413e8d187458a98633de816e4fb968e6cc" } } ], "extra": [ 1, 17, 27, 64, 245, 152, 193, 214, 28, 160, 46, 10, 138, 4, 17, 116, 199, 228, 237, 136, 214, 202, 154, 67, 143, 166, 201, 115, 96, 149, 162, 22, 35, 2, 17, 0, 0, 1, 127, 86, 195, 102, 211, 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