Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65542a4e9ef70055372579c89fbca85de9dea9ed2e04f75b457d5a9f6e756d36

Tx prefix hash: b9e1f902deff9cb693665dccb694d1c0710e8ddb9ebee697bf0a7353aaf83280
Tx public key: 16f0f47a9065dd5efbc640c7007ae6fbba02876a0be37aade7def620ba324454
Timestamp: 1697422369 Timestamp [UCT]: 2023-10-16 02:12:49 Age [y:d:h:m:s]: 01:174:09:36:06
Block: 870579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385664 RingCT/type: yes/0
Extra: 0116f0f47a9065dd5efbc640c7007ae6fbba02876a0be37aade7def620ba32445402110000000133af99f4000000000000000000

1 output(s) for total of 0.800590449000 dcy

stealth address amount amount idx
00: 16f313fee0f998839051e55cc163b07269dafa0e7472a89ba47dc2411412b5e6 0.800590449000 1325462 of 0

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": 870589, "vin": [ { "gen": { "height": 870579 } } ], "vout": [ { "amount": 800590449, "target": { "key": "16f313fee0f998839051e55cc163b07269dafa0e7472a89ba47dc2411412b5e6" } } ], "extra": [ 1, 22, 240, 244, 122, 144, 101, 221, 94, 251, 198, 64, 199, 0, 122, 230, 251, 186, 2, 135, 106, 11, 227, 122, 173, 231, 222, 246, 32, 186, 50, 68, 84, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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