Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 185be6705d1568c3eacdba52c9a6f66ec62112574af7f0f888194e7c464a20dd

Tx prefix hash: 14f8a8bf63d44c8ab45e9ddb76afc9a4f356d1182d96ed834117d58158273466
Tx public key: c8e580c6a3e1e12050fdacba0776012fb6d9082fca75aab7b3a59a22d2cec457
Timestamp: 1708020262 Timestamp [UCT]: 2024-02-15 18:04:22 Age [y:d:h:m:s]: 01:042:17:23:08
Block: 958229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291576 RingCT/type: yes/0
Extra: 01c8e580c6a3e1e12050fdacba0776012fb6d9082fca75aab7b3a59a22d2cec45702110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0715c34b1e3998123a3008f91d21797cc6766a0e6b15a186acdb2c36be632197 0.600000000000 1417588 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": 958239, "vin": [ { "gen": { "height": 958229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0715c34b1e3998123a3008f91d21797cc6766a0e6b15a186acdb2c36be632197" } } ], "extra": [ 1, 200, 229, 128, 198, 163, 225, 225, 32, 80, 253, 172, 186, 7, 118, 1, 47, 182, 217, 8, 47, 202, 117, 170, 183, 179, 165, 154, 34, 210, 206, 196, 87, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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