Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1fedd5fa7a3f9eed31511aab1be8c2e042584e2cffdfad10d5367a6b67a0d6a

Tx prefix hash: 17b81a53175529feb0cbd8b9060d274545795afec45bcf8313fbceef8765d69d
Tx public key: bbdbf87fc5f64b61e11d34bce337e167f5a92cee724bc5643007ac54b4e73b9e
Timestamp: 1761688854 Timestamp [UTC]: 2025-10-28 22:00:54 Age [y:d:h:m:s]: 01:018:17:36:29
Block: 1400072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279668 RingCT/type: yes/0
Extra: 01bbdbf87fc5f64b61e11d34bce337e167f5a92cee724bc5643007ac54b4e73b9e02110000000125a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d2e443796756d7f60f169e9baf89bb7cbc2b3be4adc9e0997a46027860b288a6 0.000600000000 1888379 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": 1400082, "vin": [ { "gen": { "height": 1400072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2e443796756d7f60f169e9baf89bb7cbc2b3be4adc9e0997a46027860b288a6" } } ], "extra": [ 1, 187, 219, 248, 127, 197, 246, 75, 97, 225, 29, 52, 188, 227, 55, 225, 103, 245, 169, 44, 238, 114, 75, 197, 100, 48, 7, 172, 84, 180, 231, 59, 158, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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: