Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36fcba3cf27fffa5d5d2b696d9b145d45327410f9b9063c213e9877d15669b9f

Tx prefix hash: 68b61ad6526814208d27780474f55929784308d4f58ae4262bc5952e65e5848d
Tx public key: 7ed66d0c83425e381a0960f7a1532f373ee7a217ea441a57c324c1fedb9929c4
Timestamp: 1721788679 Timestamp [UCT]: 2024-07-24 02:37:59 Age [y:d:h:m:s]: 01:135:08:17:59
Block: 1072379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355258 RingCT/type: yes/0
Extra: 017ed66d0c83425e381a0960f7a1532f373ee7a217ea441a57c324c1fedb9929c4021100000014e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00e5d5e6ea082bb890e2d11d35bac2536d5d5ee43509c3bc7ffa253a2408ea79 0.600000000000 1544844 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": 1072389, "vin": [ { "gen": { "height": 1072379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00e5d5e6ea082bb890e2d11d35bac2536d5d5ee43509c3bc7ffa253a2408ea79" } } ], "extra": [ 1, 126, 214, 109, 12, 131, 66, 94, 56, 26, 9, 96, 247, 161, 83, 47, 55, 62, 231, 162, 23, 234, 68, 26, 87, 195, 36, 193, 254, 219, 153, 41, 196, 2, 17, 0, 0, 0, 20, 233, 20, 221, 21, 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