Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f4b92e1b2ab2db8105ee4d187bd08912444f9b62eb7a67a978c4dea3bed4877

Tx prefix hash: eaa4a258fa1755c1823d8e2a5b1a2097953b9d62e5192f0edbb54c9899f62259
Tx public key: 50126e861a5a13c31a95ca8af68662b4e00a773c1e28dcabf85a1bdbfa8e669a
Timestamp: 1750494410 Timestamp [UCT]: 2025-06-21 08:26:50 Age [y:d:h:m:s]: 00:145:23:12:53
Block: 1309635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102174 RingCT/type: yes/0
Extra: 0150126e861a5a13c31a95ca8af68662b4e00a773c1e28dcabf85a1bdbfa8e669a021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26e5859d0cc8e4fcce378da5607b7603b76512b182b1277b0ef14febda808e82 0.600000000000 1797252 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": 1309645, "vin": [ { "gen": { "height": 1309635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26e5859d0cc8e4fcce378da5607b7603b76512b182b1277b0ef14febda808e82" } } ], "extra": [ 1, 80, 18, 110, 134, 26, 90, 19, 195, 26, 149, 202, 138, 246, 134, 98, 180, 224, 10, 119, 60, 30, 40, 220, 171, 248, 90, 27, 219, 250, 142, 102, 154, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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