Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7bfdff03eb7ef5f249fb3efde056e669453bfe69e2f30ff9fa398e24a1188d1

Tx prefix hash: 5ff31453e263a4a5f5381096079255496e823958c46febb7bcedabc4a02f5558
Tx public key: 7d0f603c7371d31d54e80c6d9bd1a177074e1aac7c5b84f5176edcf7004c3a87
Timestamp: 1771416608 Timestamp [UTC]: 2026-02-18 12:10:08 Age [y:d:h:m:s]: 00:272:10:27:00
Block: 1480463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200231 RingCT/type: yes/0
Extra: 017d0f603c7371d31d54e80c6d9bd1a177074e1aac7c5b84f5176edcf7004c3a87021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 250d1819100ee5a81331f07881597cfbbf90bf01c0884a2c5c354f2fd5907aac 0.000600000000 1969833 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": 1480473, "vin": [ { "gen": { "height": 1480463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "250d1819100ee5a81331f07881597cfbbf90bf01c0884a2c5c354f2fd5907aac" } } ], "extra": [ 1, 125, 15, 96, 60, 115, 113, 211, 29, 84, 232, 12, 109, 155, 209, 161, 119, 7, 78, 26, 172, 124, 91, 132, 245, 23, 110, 220, 247, 0, 76, 58, 135, 2, 17, 0, 0, 0, 4, 241, 136, 200, 168, 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: