Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc2d5567b56f0bd3c1d214a0fecc6f8b126d8b1b338bd6abd244b12441be198a

Tx prefix hash: c6e434385a6824a4b22014a046b10b9d301276c502bbed0a15a7544c863b25be
Tx public key: ef1c64d3af6b79e9fac6f0669b7198de9388ff6eb5ecf4013248e4773216da9e
Timestamp: 1705536039 Timestamp [UCT]: 2024-01-18 00:00:39 Age [y:d:h:m:s]: 01:307:04:59:50
Block: 937621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478399 RingCT/type: yes/0
Extra: 01ef1c64d3af6b79e9fac6f0669b7198de9388ff6eb5ecf4013248e4773216da9e0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbc6c3cadf45b325af7ebf4756a5069a8d8fe1d638b2438188c512b5451ef822 0.600000000000 1395683 of 15

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": 937631, "vin": [ { "gen": { "height": 937621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbc6c3cadf45b325af7ebf4756a5069a8d8fe1d638b2438188c512b5451ef822" } } ], "extra": [ 1, 239, 28, 100, 211, 175, 107, 121, 233, 250, 198, 240, 102, 155, 113, 152, 222, 147, 136, 255, 110, 181, 236, 244, 1, 50, 72, 228, 119, 50, 22, 218, 158, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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