Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d88eed372af40de55299b9de5bd926a72eb5aebd577181e45af3d2215384dfc

Tx prefix hash: 67c7abf370a5e5a1694466b50db79669a87a4569a78a9323982e59d250a2bc1f
Tx public key: 406ffa34c7ec5a2d26b9be4fa7b648ad39b6e4e1d6f1555c8ea505565c7263e6
Timestamp: 1578410847 Timestamp [UCT]: 2020-01-07 15:27:27 Age [y:d:h:m:s]: 04:318:22:12:46
Block: 40614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117235 RingCT/type: yes/0
Extra: 01406ffa34c7ec5a2d26b9be4fa7b648ad39b6e4e1d6f1555c8ea505565c7263e60211000000134ac5aa02000000000000000000

1 output(s) for total of 450.225205587000 dcy

stealth address amount amount idx
00: 2129230b985ad64bd230055c4c50a685e9e01689ca32dedbbd79d3e79b1520e6 450.225205587000 71469 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": 40624, "vin": [ { "gen": { "height": 40614 } } ], "vout": [ { "amount": 450225205587, "target": { "key": "2129230b985ad64bd230055c4c50a685e9e01689ca32dedbbd79d3e79b1520e6" } } ], "extra": [ 1, 64, 111, 250, 52, 199, 236, 90, 45, 38, 185, 190, 79, 167, 182, 72, 173, 57, 182, 228, 225, 214, 241, 85, 92, 142, 165, 5, 86, 92, 114, 99, 230, 2, 17, 0, 0, 0, 19, 74, 197, 170, 2, 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