Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5ec8f42869c59542d7d9a100fdbc786a1c73865be43ae5bdf092de4a993ea41

Tx prefix hash: 9ed48a0822df1e771177e2eca354361484b1b42836a720521a5a0a9923b87a8a
Tx public key: 8588517d9d128a7c1488328edf504a98e0ae7e5c3850a4ff20a87dcd83ca01d8
Timestamp: 1755905617 Timestamp [UCT]: 2025-08-22 23:33:37 Age [y:d:h:m:s]: 00:089:08:27:52
Block: 1352308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63797 RingCT/type: yes/0
Extra: 018588517d9d128a7c1488328edf504a98e0ae7e5c3850a4ff20a87dcd83ca01d80211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f17dd63e6cc106d530019a93cd8172169d3603c89d39df220280ed5e93e26b6 0.600000000000 1840271 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": 1352318, "vin": [ { "gen": { "height": 1352308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f17dd63e6cc106d530019a93cd8172169d3603c89d39df220280ed5e93e26b6" } } ], "extra": [ 1, 133, 136, 81, 125, 157, 18, 138, 124, 20, 136, 50, 142, 223, 80, 74, 152, 224, 174, 126, 92, 56, 80, 164, 255, 32, 168, 125, 205, 131, 202, 1, 216, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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