Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b694f5a4c670e70dff2f66fce2bc245f34fedeeb8992aa056ddd4b6df1b390da

Tx prefix hash: a7c868a5ad96f9120af13b04ebcc079ccf224bea15b91b449b6cf0ff8b80ca3c
Tx public key: 88efbdfa8bd9bf5514a9854fdd311a8b6540a5f5967889875715e5eebe843d0c
Timestamp: 1743112450 Timestamp [UTC]: 2025-03-27 21:54:10 Age [y:d:h:m:s]: 01:231:08:12:27
Block: 1248678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429262 RingCT/type: yes/0
Extra: 0188efbdfa8bd9bf5514a9854fdd311a8b6540a5f5967889875715e5eebe843d0c021100000001d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b9320d0d67f28faf77d6b257da7d6a3aa37e7a9f8d5e5acd99500f11c6da3f05 0.000600000000 1735711 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": 1248688, "vin": [ { "gen": { "height": 1248678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9320d0d67f28faf77d6b257da7d6a3aa37e7a9f8d5e5acd99500f11c6da3f05" } } ], "extra": [ 1, 136, 239, 189, 250, 139, 217, 191, 85, 20, 169, 133, 79, 221, 49, 26, 139, 101, 64, 165, 245, 150, 120, 137, 135, 87, 21, 229, 238, 190, 132, 61, 12, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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: