Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 403a015d5db2ca77c713b188157e050dff0df9fa060a19c0b010f42801a89140

Tx prefix hash: fd4c324d5b556c1f91c5accb1187647f04a7b649d2a11ca3d61dd732b69ac055
Tx public key: c6a7f7096f57def84b9d7e13ed6df92ea2ad476afc20e71756eec8dba9de5287
Timestamp: 1740958710 Timestamp [UCT]: 2025-03-02 23:38:30 Age [y:d:h:m:s]: 00:257:00:54:21
Block: 1230850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181456 RingCT/type: yes/0
Extra: 01c6a7f7096f57def84b9d7e13ed6df92ea2ad476afc20e71756eec8dba9de5287021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34536d0e08630cb6d915a6decf35cc1c36ecb2558f0ffc8769a322be8061998f 0.600000000000 1717753 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": 1230860, "vin": [ { "gen": { "height": 1230850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34536d0e08630cb6d915a6decf35cc1c36ecb2558f0ffc8769a322be8061998f" } } ], "extra": [ 1, 198, 167, 247, 9, 111, 87, 222, 248, 75, 157, 126, 19, 237, 109, 249, 46, 162, 173, 71, 106, 252, 32, 231, 23, 86, 238, 200, 219, 169, 222, 82, 135, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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