Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 657f299e70ae8d5dfc77c7c96d0d091620525428d90e3d88f9d2ebfc377680d1

Tx prefix hash: 032a4e3715c73f9482a69d103187c8c0107c9e9ec754763fa4a9f57229970741
Tx public key: fe3cc2ae76c719b246a00aa62490a459eff52501e0799b2c495a14f2d9f82807
Timestamp: 1764630961 Timestamp [UCT]: 2025-12-01 23:16:01 Age [y:d:h:m:s]: 00:003:06:31:12
Block: 1424437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2350 RingCT/type: yes/0
Extra: 01fe3cc2ae76c719b246a00aa62490a459eff52501e0799b2c495a14f2d9f82807021100000004da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b2e882161708e0c21828f3a382feaeea347aa3af548657e933dfc7d2fd50aaf 0.600000000000 1913068 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": 1424447, "vin": [ { "gen": { "height": 1424437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b2e882161708e0c21828f3a382feaeea347aa3af548657e933dfc7d2fd50aaf" } } ], "extra": [ 1, 254, 60, 194, 174, 118, 199, 25, 178, 70, 160, 10, 166, 36, 144, 164, 89, 239, 245, 37, 1, 224, 121, 155, 44, 73, 90, 20, 242, 217, 248, 40, 7, 2, 17, 0, 0, 0, 4, 218, 85, 72, 72, 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