Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b06e0c688696d8e815e8e864b3c6e1d7adafba2a5e06551be2d4b95bb294ff8a

Tx prefix hash: f4cb5ad9ef4b90c9daab3688b3d939f9302f1f78b96cbedc2e6993be34b1629f
Tx public key: 151492b3f859098a4c4240011573a301aed74a60c1a852e401213f202f5ceb53
Timestamp: 1752065761 Timestamp [UTC]: 2025-07-09 12:56:01 Age [y:d:h:m:s]: 01:128:05:37:33
Block: 1321944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356381 RingCT/type: yes/0
Extra: 01151492b3f859098a4c4240011573a301aed74a60c1a852e401213f202f5ceb53021100000001d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 98ae40f6031078ccd9c4974f2b2f008a4fd23272205ad43041c6512e4bf8a90f 0.000600000000 1809653 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": 1321954, "vin": [ { "gen": { "height": 1321944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98ae40f6031078ccd9c4974f2b2f008a4fd23272205ad43041c6512e4bf8a90f" } } ], "extra": [ 1, 21, 20, 146, 179, 248, 89, 9, 138, 76, 66, 64, 1, 21, 115, 163, 1, 174, 215, 74, 96, 193, 168, 82, 228, 1, 33, 63, 32, 47, 92, 235, 83, 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: