Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0996105dc0e14edd83177fd6347769aac07aa991ae53b37e5ecbaf6dc3ba9854

Tx prefix hash: c1077a6c4878a13edede82c9d2faa945a95503ac00ae5e4ab7754c07ab194d15
Tx public key: a80876bcd9f6f822d88f750cc092abd48e6d10a8cc7aca6e960621382d433e9c
Timestamp: 1737062584 Timestamp [UCT]: 2025-01-16 21:23:04 Age [y:d:h:m:s]: 00:155:14:24:54
Block: 1198855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110876 RingCT/type: yes/0
Extra: 01a80876bcd9f6f822d88f750cc092abd48e6d10a8cc7aca6e960621382d433e9c0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08bbd470e318f373b4e4ea49412616e9082beefaf5b239ae3b50cd1f1ef82de3 0.600000000000 1685482 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": 1198865, "vin": [ { "gen": { "height": 1198855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08bbd470e318f373b4e4ea49412616e9082beefaf5b239ae3b50cd1f1ef82de3" } } ], "extra": [ 1, 168, 8, 118, 188, 217, 246, 248, 34, 216, 143, 117, 12, 192, 146, 171, 212, 142, 109, 16, 168, 204, 122, 202, 110, 150, 6, 33, 56, 45, 67, 62, 156, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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