Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 650d7ced342044eea0d5b7f9464c1bdd05fbb15cfe35045bb16442f9c25acb4d

Tx prefix hash: f986b3e7e395a423e5fe070be97a8df4f8b371888f8b69f0e3a06afabc4edb96
Tx public key: b524bf76b1a36cd0f70384c49f648dbb390e4aa9440755a7b3f1b7ad32cf8f93
Timestamp: 1740667268 Timestamp [UCT]: 2025-02-27 14:41:08 Age [y:d:h:m:s]: 00:266:03:03:17
Block: 1228425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187964 RingCT/type: yes/0
Extra: 01b524bf76b1a36cd0f70384c49f648dbb390e4aa9440755a7b3f1b7ad32cf8f930211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cd46e102501d41f071dd63a60dea3fc22688998b83ebd6c1aa2a57d969d0244 0.600000000000 1715306 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": 1228435, "vin": [ { "gen": { "height": 1228425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cd46e102501d41f071dd63a60dea3fc22688998b83ebd6c1aa2a57d969d0244" } } ], "extra": [ 1, 181, 36, 191, 118, 177, 163, 108, 208, 247, 3, 132, 196, 159, 100, 141, 187, 57, 14, 74, 169, 68, 7, 85, 167, 179, 241, 183, 173, 50, 207, 143, 147, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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