Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fee3cde1e23c4061cbe220ff17b6de983ac1b06b365e9c2ab3369d86068ec33

Tx prefix hash: 2c7865b84117573f9921f82ac13bc25c3301d05abd06cc7e78f7d1f9952eb89e
Tx public key: e91072b2cae97e931c68900bf2fc43ba54067cb54818d1dfa0068358b3a94a18
Timestamp: 1703639434 Timestamp [UCT]: 2023-12-27 01:10:34 Age [y:d:h:m:s]: 01:138:07:38:30
Block: 921918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359996 RingCT/type: yes/0
Extra: 01e91072b2cae97e931c68900bf2fc43ba54067cb54818d1dfa0068358b3a94a1802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6aa2d0705fce8ec70c294a27d9b14c952af6243cf24f57720a2e4b1d344b962b 0.600000000000 1379612 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": 921928, "vin": [ { "gen": { "height": 921918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6aa2d0705fce8ec70c294a27d9b14c952af6243cf24f57720a2e4b1d344b962b" } } ], "extra": [ 1, 233, 16, 114, 178, 202, 233, 126, 147, 28, 104, 144, 11, 242, 252, 67, 186, 84, 6, 124, 181, 72, 24, 209, 223, 160, 6, 131, 88, 179, 169, 74, 24, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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