Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e443514ca781fa02944810fe1213b6c4cf319949724220e59a61b7e72a316482

Tx prefix hash: 5292341e96a082bdfe442194888f4ebf6d70d3282ae11b1344790ed302e4cc92
Tx public key: 138d4e9c2b89355ea568013ad04e3c5f805f85047f75afeea2a0f1a1b6fe5ff7
Timestamp: 1710207804 Timestamp [UCT]: 2024-03-12 01:43:24 Age [y:d:h:m:s]: 01:241:16:32:53
Block: 976386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431437 RingCT/type: yes/0
Extra: 01138d4e9c2b89355ea568013ad04e3c5f805f85047f75afeea2a0f1a1b6fe5ff70211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd22ed26dc32eaae6834a4cb0c6e976151556c6d5fd29857e63f59e3b7c695b7 0.600000000000 1436379 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": 976396, "vin": [ { "gen": { "height": 976386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd22ed26dc32eaae6834a4cb0c6e976151556c6d5fd29857e63f59e3b7c695b7" } } ], "extra": [ 1, 19, 141, 78, 156, 43, 137, 53, 94, 165, 104, 1, 58, 208, 78, 60, 95, 128, 95, 133, 4, 127, 117, 175, 238, 162, 160, 241, 161, 182, 254, 95, 247, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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