Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad3e9d5a856339431657764dce042f5779dea1b8dbcc23cef7c6a1503b294b26

Tx prefix hash: 7f7534da3d67f927c26189d9611905766be09a0df8915477d8530463678a1b5d
Tx public key: 5e43eaccdb073e103fd4a4a26cdc2406264dcd6b3d57800f6dd38bc4cdc23106
Timestamp: 1703447233 Timestamp [UCT]: 2023-12-24 19:47:13 Age [y:d:h:m:s]: 01:170:18:27:41
Block: 920328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383178 RingCT/type: yes/0
Extra: 015e43eaccdb073e103fd4a4a26cdc2406264dcd6b3d57800f6dd38bc4cdc2310602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 341e7826b109ab3c9758f6b4ec5111df68aec782f362e71b9d971cea935f1c3a 0.600000000000 1378006 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": 920338, "vin": [ { "gen": { "height": 920328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "341e7826b109ab3c9758f6b4ec5111df68aec782f362e71b9d971cea935f1c3a" } } ], "extra": [ 1, 94, 67, 234, 204, 219, 7, 62, 16, 63, 212, 164, 162, 108, 220, 36, 6, 38, 77, 205, 107, 61, 87, 128, 15, 109, 211, 139, 196, 205, 194, 49, 6, 2, 17, 0, 0, 0, 3, 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