Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f95e28eb52f3e93db23981979cac0753a9223823dea8f917ef07e026abaeb0bb

Tx prefix hash: 03f504cdf94ed2ef102af1217c563ce8f2b72b13c210e1488ce12b421003184d
Tx public key: 68ffcaa8a8d3e6c801cf32acd42a07d9acfedb616be9b5249157272c23f20966
Timestamp: 1741168215 Timestamp [UTC]: 2025-03-05 09:50:15 Age [y:d:h:m:s]: 01:067:18:24:01
Block: 1232594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299237 RingCT/type: yes/0
Extra: 0168ffcaa8a8d3e6c801cf32acd42a07d9acfedb616be9b5249157272c23f209660211000000091f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8101e6d36f3bc66a2f33b2ff5a7339976bb6ca37311f4a615a6819ef632a411b 0.000600000000 1719507 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": 1232604, "vin": [ { "gen": { "height": 1232594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8101e6d36f3bc66a2f33b2ff5a7339976bb6ca37311f4a615a6819ef632a411b" } } ], "extra": [ 1, 104, 255, 202, 168, 168, 211, 230, 200, 1, 207, 50, 172, 212, 42, 7, 217, 172, 254, 219, 97, 107, 233, 181, 36, 145, 87, 39, 44, 35, 242, 9, 102, 2, 17, 0, 0, 0, 9, 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: