Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80b7db52323c11ef19decd79dda92092f53f8e5f969038b1beb6a4d180659706

Tx prefix hash: a5c8d4866b5999c0116abc9d7b87fa7cff2e3fa8a96568665166845507b21882
Tx public key: 7a4881ef8c9e94913c8232a779045ae51d2321d702dc2a47dba4e1b35b12d282
Timestamp: 1727027999 Timestamp [UCT]: 2024-09-22 17:59:59 Age [y:d:h:m:s]: 00:191:03:30:28
Block: 1115824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136409 RingCT/type: yes/0
Extra: 017a4881ef8c9e94913c8232a779045ae51d2321d702dc2a47dba4e1b35b12d28202110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e791825d2d28d4406ef9b0063bfb595af64448494c1c2972d80a2e48a25db546 0.600000000000 1596089 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": 1115834, "vin": [ { "gen": { "height": 1115824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e791825d2d28d4406ef9b0063bfb595af64448494c1c2972d80a2e48a25db546" } } ], "extra": [ 1, 122, 72, 129, 239, 140, 158, 148, 145, 60, 130, 50, 167, 121, 4, 90, 229, 29, 35, 33, 215, 2, 220, 42, 71, 219, 164, 225, 179, 91, 18, 210, 130, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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