Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d830b8c4af093ca46aea0151aec3d52c1df15e60048a4abb3a3e13b9f47f7b9

Tx prefix hash: 917bcf229998d908c9d7d0377eda194fba62e51f88d2e07b4d5e10b51b7ebb0d
Tx public key: 6f7af10ea96027cfea36e885ce50eedd317b97e42ebb06bb7da2d4f615a58641
Timestamp: 1728455504 Timestamp [UCT]: 2024-10-09 06:31:44 Age [y:d:h:m:s]: 00:046:04:20:33
Block: 1127654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32983 RingCT/type: yes/0
Extra: 016f7af10ea96027cfea36e885ce50eedd317b97e42ebb06bb7da2d4f615a58641021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c30c40095cba4c351adf42e3adb7bd4f996495347b1713729cf6b6d589549301 0.600000000000 1610461 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": 1127664, "vin": [ { "gen": { "height": 1127654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c30c40095cba4c351adf42e3adb7bd4f996495347b1713729cf6b6d589549301" } } ], "extra": [ 1, 111, 122, 241, 14, 169, 96, 39, 207, 234, 54, 232, 133, 206, 80, 238, 221, 49, 123, 151, 228, 46, 187, 6, 187, 125, 162, 212, 246, 21, 165, 134, 65, 2, 17, 0, 0, 0, 1, 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