Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53e958607cfc9fd38080c595d2c3bc6aecba4f72f106fdfcfec037b04c3c0684

Tx prefix hash: 43c59b7beba651be87cbaa06f780a97859cfecc9bc1b2b1bb8863b386a171593
Tx public key: eed83a8670ac397cf0f74d726789ddcc1b33dca644d7ac28e5a12827aa91b1db
Timestamp: 1764917980 Timestamp [UTC]: 2025-12-05 06:59:40 Age [y:d:h:m:s]: 00:345:15:18:58
Block: 1426825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252373 RingCT/type: yes/0
Extra: 01eed83a8670ac397cf0f74d726789ddcc1b33dca644d7ac28e5a12827aa91b1db02110000000470609d03000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 85b5a3cc2d0502cf2611e0cf39e60c2eb6fae7156556dda4149a4dc3bfb74e1e 0.000600000000 1915518 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 dinastycoin-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": 1426835, "vin": [ { "gen": { "height": 1426825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85b5a3cc2d0502cf2611e0cf39e60c2eb6fae7156556dda4149a4dc3bfb74e1e" } } ], "extra": [ 1, 238, 216, 58, 134, 112, 172, 57, 124, 240, 247, 77, 114, 103, 137, 221, 204, 27, 51, 220, 166, 68, 215, 172, 40, 229, 161, 40, 39, 170, 145, 177, 219, 2, 17, 0, 0, 0, 4, 112, 96, 157, 3, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: