Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98209bbca17e03a0fdd9ad606b413b345facec1d86e6f4215f5ed4832898533a

Tx prefix hash: 7ea403788f32aae46a3e3709ea225ab651745b29e76e9594c75792df1b8c25cf
Tx public key: f69d9616a8f799fbffcd2f536c2df89a7cc191ce568ec44f4131f1682ece3c39
Timestamp: 1740609243 Timestamp [UTC]: 2025-02-26 22:34:03 Age [y:d:h:m:s]: 01:179:11:40:07
Block: 1227950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392667 RingCT/type: yes/0
Extra: 01f69d9616a8f799fbffcd2f536c2df89a7cc191ce568ec44f4131f1682ece3c390211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bbb327ebdfd7695cd0d1951765e16b39e4ced1d5a8971391b436d18bd23bf8cb 0.000600000000 1714827 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": 1227960, "vin": [ { "gen": { "height": 1227950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbb327ebdfd7695cd0d1951765e16b39e4ced1d5a8971391b436d18bd23bf8cb" } } ], "extra": [ 1, 246, 157, 150, 22, 168, 247, 153, 251, 255, 205, 47, 83, 108, 45, 248, 154, 124, 193, 145, 206, 86, 142, 196, 79, 65, 49, 241, 104, 46, 206, 60, 57, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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: