Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a8c8a5599cda8aca94728ff45bd58c329d0951c4c1c6a44ab46391e1d3b4809

Tx prefix hash: 2441a0bf8bc7dfd70664b15eadf65e06950f9a6c0e25c1f11601c21a457639c2
Tx public key: 6312e33de92cda629a2cb2bfe67b6dc557f069c8ac3410f8541cde736bb14813
Timestamp: 1703602553 Timestamp [UCT]: 2023-12-26 14:55:53 Age [y:d:h:m:s]: 01:061:14:07:19
Block: 921613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305098 RingCT/type: yes/0
Extra: 016312e33de92cda629a2cb2bfe67b6dc557f069c8ac3410f8541cde736bb148130211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24209a502d330ad1b9a41aecb5b006421345319867b2d8eea4be4391df3575c7 0.600000000000 1379303 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": 921623, "vin": [ { "gen": { "height": 921613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24209a502d330ad1b9a41aecb5b006421345319867b2d8eea4be4391df3575c7" } } ], "extra": [ 1, 99, 18, 227, 61, 233, 44, 218, 98, 154, 44, 178, 191, 230, 123, 109, 197, 87, 240, 105, 200, 172, 52, 16, 248, 84, 28, 222, 115, 107, 177, 72, 19, 2, 17, 0, 0, 0, 5, 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