Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8859542c08377d4dbda09435eeda1cf6c1eae763d9d565cd1ccacbd17a6c4437

Tx prefix hash: aaa09ae052c9376f1b204ee34ba36e8c7bd81d22abed9d0e56fb086b7d682d00
Tx public key: 32da089cd9e6c567efdf9d9c0ff74d538b0c48baa895d08f0946a8f3ec708716
Timestamp: 1737195524 Timestamp [UCT]: 2025-01-18 10:18:44 Age [y:d:h:m:s]: 00:151:08:17:59
Block: 1199966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107861 RingCT/type: yes/0
Extra: 0132da089cd9e6c567efdf9d9c0ff74d538b0c48baa895d08f0946a8f3ec7087160211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5122442e1cc62631b82da948404b03c28e8f998659054e873d76fbfb05531eb 0.600000000000 1686607 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": 1199976, "vin": [ { "gen": { "height": 1199966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5122442e1cc62631b82da948404b03c28e8f998659054e873d76fbfb05531eb" } } ], "extra": [ 1, 50, 218, 8, 156, 217, 230, 197, 103, 239, 223, 157, 156, 15, 247, 77, 83, 139, 12, 72, 186, 168, 149, 208, 143, 9, 70, 168, 243, 236, 112, 135, 22, 2, 17, 0, 0, 0, 2, 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