Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad9129b4a1894d855fb6defda50cf8b3da2d2c4d909670d321164fe90555bc8e

Tx prefix hash: b7a5e4dc07cdf313816d5d909d0ed238621495ba2b97e85d42f83e64f548ad2a
Tx public key: 6c4298e0c373eba8223a1cff63ca94742f22b14c3a271db85e7ce3b7254b218a
Timestamp: 1760706263 Timestamp [UTC]: 2025-10-17 13:04:23 Age [y:d:h:m:s]: 01:027:07:21:23
Block: 1391921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285717 RingCT/type: yes/0
Extra: 016c4298e0c373eba8223a1cff63ca94742f22b14c3a271db85e7ce3b7254b218a0211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6dd8e3ca1b54405df07fcc1900d017d7b7e429efdd0280ca85f909ca80555dfd 0.000600000000 1880170 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": 1391931, "vin": [ { "gen": { "height": 1391921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dd8e3ca1b54405df07fcc1900d017d7b7e429efdd0280ca85f909ca80555dfd" } } ], "extra": [ 1, 108, 66, 152, 224, 195, 115, 235, 168, 34, 58, 28, 255, 99, 202, 148, 116, 47, 34, 177, 76, 58, 39, 29, 184, 94, 124, 227, 183, 37, 75, 33, 138, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: