Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76d4738a01c2dd960fe23eaa13c62032afc7df8c017d2ac6a3a6458e8084139c

Tx prefix hash: e3e1601ca589ed386a46fdfb9dd2aab65838d43f8cd68953b1d9bd1f738c1740
Tx public key: 78837e7160b4312e9d9ded1adbb8bdd2ac46f9ad7128d33b4d47c23e2c8dfc0c
Timestamp: 1721113466 Timestamp [UCT]: 2024-07-16 07:04:26 Age [y:d:h:m:s]: 00:266:19:33:35
Block: 1066799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190604 RingCT/type: yes/0
Extra: 0178837e7160b4312e9d9ded1adbb8bdd2ac46f9ad7128d33b4d47c23e2c8dfc0c021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 463b2c80812c97529105b891643e21cffea6578959487d9809aeedcec3a4be55 0.600000000000 1537466 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": 1066809, "vin": [ { "gen": { "height": 1066799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "463b2c80812c97529105b891643e21cffea6578959487d9809aeedcec3a4be55" } } ], "extra": [ 1, 120, 131, 126, 113, 96, 180, 49, 46, 157, 157, 237, 26, 219, 184, 189, 210, 172, 70, 249, 173, 113, 40, 211, 59, 77, 71, 194, 62, 44, 141, 252, 12, 2, 17, 0, 0, 0, 6, 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