Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd50536481e077e983b3e3d5c272a821193011f371b8ef8f6aa909c143109632

Tx prefix hash: 84d349d35ec4baabf9640445c6a0c8ff31055891338635e059d7fcc004a1f6ca
Tx public key: e54bdd19a9ad0d0e381dc50e7a6becbb9d80de36bdbde045e57b593cb5d98803
Timestamp: 1720608521 Timestamp [UCT]: 2024-07-10 10:48:41 Age [y:d:h:m:s]: 00:292:03:37:21
Block: 1062607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208752 RingCT/type: yes/0
Extra: 01e54bdd19a9ad0d0e381dc50e7a6becbb9d80de36bdbde045e57b593cb5d9880302110000001491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9cfe12f9f648e59901881345190f1e63a0684cf791a1097b7a163d08b735188 0.600000000000 1533112 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": 1062617, "vin": [ { "gen": { "height": 1062607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9cfe12f9f648e59901881345190f1e63a0684cf791a1097b7a163d08b735188" } } ], "extra": [ 1, 229, 75, 221, 25, 169, 173, 13, 14, 56, 29, 197, 14, 122, 107, 236, 187, 157, 128, 222, 54, 189, 189, 224, 69, 229, 123, 89, 60, 181, 217, 136, 3, 2, 17, 0, 0, 0, 20, 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