Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c34ccbc30ad1cd38fec5dc4f14bea0e2456022ebc0a3ad3f69aac968dc18c18a

Tx prefix hash: a456e51185fb519965b62c13d84cfc0704fb7d94b2b2e58f7c2ec22ee315c164
Tx public key: 4b5628296f4eb3c1154e57e52c1536e89308e70e7155a087f82c96cfd7109985
Timestamp: 1704187140 Timestamp [UCT]: 2024-01-02 09:19:00 Age [y:d:h:m:s]: 01:017:23:49:44
Block: 926451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274162 RingCT/type: yes/0
Extra: 014b5628296f4eb3c1154e57e52c1536e89308e70e7155a087f82c96cfd71099850211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86dc83fc8e0a3dd9f613dd85bf32776af9e26ee4c96353ba8270b10b7690022a 0.600000000000 1384235 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": 926461, "vin": [ { "gen": { "height": 926451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86dc83fc8e0a3dd9f613dd85bf32776af9e26ee4c96353ba8270b10b7690022a" } } ], "extra": [ 1, 75, 86, 40, 41, 111, 78, 179, 193, 21, 78, 87, 229, 44, 21, 54, 232, 147, 8, 231, 14, 113, 85, 160, 135, 248, 44, 150, 207, 215, 16, 153, 133, 2, 17, 0, 0, 0, 1, 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