Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24504bb7b12b4460079820e09b42ce3cbbea71c8544c996bbd1888a7791f7964

Tx prefix hash: 89c872eed9eba6f7318fd1b3d5c4ccc74144bc144f5ea1e0ee9dfc9dd4c1fa09
Tx public key: d2203c2c157c298b48608618476f01b51eadb802e1c94ba1fc7e36bc5ba7fd93
Timestamp: 1760853021 Timestamp [UCT]: 2025-10-19 05:50:21 Age [y:d:h:m:s]: 00:032:02:32:40
Block: 1393143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22971 RingCT/type: yes/0
Extra: 01d2203c2c157c298b48608618476f01b51eadb802e1c94ba1fc7e36bc5ba7fd93021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4e17f879334c376fde22cc6632ae8dd51587f2058549eef86fdf789c4eb31e7 0.600000000000 1881402 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": 1393153, "vin": [ { "gen": { "height": 1393143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4e17f879334c376fde22cc6632ae8dd51587f2058549eef86fdf789c4eb31e7" } } ], "extra": [ 1, 210, 32, 60, 44, 21, 124, 41, 139, 72, 96, 134, 24, 71, 111, 1, 181, 30, 173, 184, 2, 225, 201, 75, 161, 252, 126, 54, 188, 91, 167, 253, 147, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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