Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eade6c72b2e25ddce918d19b37f72106e6a21e9e7315bc2661ad77b73e8c0671

Tx prefix hash: a49d4549b940283d889b52dbda2d31addf22cdf5d829c87a23393834e46d7643
Tx public key: 50e261bf6d9ca16ddb59c55de6475a898e3a3213f1c68c7484d725535b262fca
Timestamp: 1745377030 Timestamp [UCT]: 2025-04-23 02:57:10 Age [y:d:h:m:s]: 00:018:09:13:52
Block: 1267423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13161 RingCT/type: yes/0
Extra: 0150e261bf6d9ca16ddb59c55de6475a898e3a3213f1c68c7484d725535b262fca021100000002dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9cf68e19d0dcf3e074f8d32410e75b06d035930f79defa60d3aa33a03e6acf1 0.600000000000 1754652 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": 1267433, "vin": [ { "gen": { "height": 1267423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9cf68e19d0dcf3e074f8d32410e75b06d035930f79defa60d3aa33a03e6acf1" } } ], "extra": [ 1, 80, 226, 97, 191, 109, 156, 161, 109, 219, 89, 197, 93, 230, 71, 90, 137, 142, 58, 50, 19, 241, 198, 140, 116, 132, 215, 37, 83, 91, 38, 47, 202, 2, 17, 0, 0, 0, 2, 219, 181, 113, 193, 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