Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 621c8949e3c7c07111a3142f5bbf0ac33a93d0564343c82c985385aeca30c794

Tx prefix hash: 289e07a5a0b250c068a56c081b4476bf600c244c638f0732a67971b9f59d77db
Tx public key: f12dc0316a4a2f639a3e0e52c9cc0b7aa4a330ba0d669da76471bf9a7a5efbe7
Timestamp: 1753462180 Timestamp [UCT]: 2025-07-25 16:49:40 Age [y:d:h:m:s]: 00:123:23:34:05
Block: 1333206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87454 RingCT/type: yes/0
Extra: 01f12dc0316a4a2f639a3e0e52c9cc0b7aa4a330ba0d669da76471bf9a7a5efbe702110000000fef221485000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24405723ece2b67ff71b38eaf979091a4bd09724f2c89322d4e81dae361604d6 0.600000000000 1821005 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": 1333216, "vin": [ { "gen": { "height": 1333206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24405723ece2b67ff71b38eaf979091a4bd09724f2c89322d4e81dae361604d6" } } ], "extra": [ 1, 241, 45, 192, 49, 106, 74, 47, 99, 154, 62, 14, 82, 201, 204, 11, 122, 164, 163, 48, 186, 13, 102, 157, 167, 100, 113, 191, 154, 122, 94, 251, 231, 2, 17, 0, 0, 0, 15, 239, 34, 20, 133, 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