Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 384df398f5f8806ed84cd1665b4d1fb46f2e82d5c988ee0654b1d818b4d65435

Tx prefix hash: 169dabf8d158444b08adb102a32abf317d1deb253f9e0dfb595d9c945838c1f2
Tx public key: 7606f970aff71626f12b9b9f27662c4c0fcd6e68251e942912ca2662a03373cb
Timestamp: 1734649538 Timestamp [UCT]: 2024-12-19 23:05:38 Age [y:d:h:m:s]: 00:146:17:53:41
Block: 1178917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104669 RingCT/type: yes/0
Extra: 017606f970aff71626f12b9b9f27662c4c0fcd6e68251e942912ca2662a03373cb0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 565e972c32bd1707b774212ac83823775f43851ab5690fb3d52488e029e87f2e 0.600000000000 1665308 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": 1178927, "vin": [ { "gen": { "height": 1178917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "565e972c32bd1707b774212ac83823775f43851ab5690fb3d52488e029e87f2e" } } ], "extra": [ 1, 118, 6, 249, 112, 175, 247, 22, 38, 241, 43, 155, 159, 39, 102, 44, 76, 15, 205, 110, 104, 37, 30, 148, 41, 18, 202, 38, 98, 160, 51, 115, 203, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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