Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10bf8d7b612d6bb05f5610fc20555588a303a51d6ac0930cf30ab37b9b8504f5

Tx prefix hash: a22cff4959f87ffe7cb3e4360b5b7974de0be069e292df204e56d256db750d59
Tx public key: 502cd819abddba8f99944be3b066bcd2e1fba968f7917d05888ef94655dc9c6e
Timestamp: 1709361485 Timestamp [UCT]: 2024-03-02 06:38:05 Age [y:d:h:m:s]: 01:038:04:29:59
Block: 969355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288311 RingCT/type: yes/0
Extra: 01502cd819abddba8f99944be3b066bcd2e1fba968f7917d05888ef94655dc9c6e0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c34b55c2ffa7f22ec8c9c64fa1111c77852407411766c08964d0fb908fd9dd1 0.600000000000 1429184 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": 969365, "vin": [ { "gen": { "height": 969355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c34b55c2ffa7f22ec8c9c64fa1111c77852407411766c08964d0fb908fd9dd1" } } ], "extra": [ 1, 80, 44, 216, 25, 171, 221, 186, 143, 153, 148, 75, 227, 176, 102, 188, 210, 225, 251, 169, 104, 247, 145, 125, 5, 136, 142, 249, 70, 85, 220, 156, 110, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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