Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c51d92445dfba41635848996e28aeadc7e09ff28be194e38c2d662d83b5cd3c8

Tx prefix hash: 28c2d37e088a078e6fb33e72849af7dc1e33ff04f1bb9b096e0aeb1cb85016d0
Tx public key: a39836e90a8972bb3598d1fdd38ee33feeb5b96ed089d9beb6eff54fa2d5d2be
Timestamp: 1727720183 Timestamp [UCT]: 2024-09-30 18:16:23 Age [y:d:h:m:s]: 00:187:03:06:28
Block: 1121563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133536 RingCT/type: yes/0
Extra: 01a39836e90a8972bb3598d1fdd38ee33feeb5b96ed089d9beb6eff54fa2d5d2be02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b40356cc334d47d37847b5902b558a109dc8ff081ef39d3b11803b070f7fcdf 0.600000000000 1603852 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": 1121573, "vin": [ { "gen": { "height": 1121563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b40356cc334d47d37847b5902b558a109dc8ff081ef39d3b11803b070f7fcdf" } } ], "extra": [ 1, 163, 152, 54, 233, 10, 137, 114, 187, 53, 152, 209, 253, 211, 142, 227, 63, 238, 181, 185, 110, 208, 137, 217, 190, 182, 239, 245, 79, 162, 213, 210, 190, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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