Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 553ac890fdd2c9e867bcb0bb91580cd0092e70b0f84ef02d3b8495c3154fef07

Tx prefix hash: bd4cf45be9b76db948b023c136f8168ab6b261de7c8c6622670c647c4e7c0d11
Tx public key: 722641dd6cdaf9ccd64f780d874affa41ce896f4e0ea84ce94fa5e1a0f38fedc
Timestamp: 1750837972 Timestamp [UCT]: 2025-06-25 07:52:52 Age [y:d:h:m:s]: 00:142:02:53:30
Block: 1312380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99513 RingCT/type: yes/0
Extra: 01722641dd6cdaf9ccd64f780d874affa41ce896f4e0ea84ce94fa5e1a0f38fedc021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d02688904b2643763bd253c52e2347215740da7340d7f7f18b7a1a7e06200e4b 0.600000000000 1800013 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": 1312390, "vin": [ { "gen": { "height": 1312380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d02688904b2643763bd253c52e2347215740da7340d7f7f18b7a1a7e06200e4b" } } ], "extra": [ 1, 114, 38, 65, 221, 108, 218, 249, 204, 214, 79, 120, 13, 135, 74, 255, 164, 28, 232, 150, 244, 224, 234, 132, 206, 148, 250, 94, 26, 15, 56, 254, 220, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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