Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9aa1f98517093e7cb12ce20fb90536eaf75ea2dfa00dc20b31bd342ecc0864c

Tx prefix hash: 26b2396e86d9698831dbbfb403a2bb9f89e095392d9c5e01572d8a3764834847
Tx public key: 9b8d67a593533f0ef14ec27856f11ff342fac3c2ea9750fa4c12f07af6ca90d1
Timestamp: 1750090153 Timestamp [UTC]: 2025-06-16 16:09:13 Age [y:d:h:m:s]: 01:155:08:39:16
Block: 1306350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375161 RingCT/type: yes/0
Extra: 019b8d67a593533f0ef14ec27856f11ff342fac3c2ea9750fa4c12f07af6ca90d1021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1ecebbbf7ea911937560996c3b5a0f74ad5a9d58627aef3024a3274a22120a69 0.000600000000 1793955 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": 1306360, "vin": [ { "gen": { "height": 1306350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ecebbbf7ea911937560996c3b5a0f74ad5a9d58627aef3024a3274a22120a69" } } ], "extra": [ 1, 155, 141, 103, 165, 147, 83, 63, 14, 241, 78, 194, 120, 86, 241, 31, 243, 66, 250, 195, 194, 234, 151, 80, 250, 76, 18, 240, 122, 246, 202, 144, 209, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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: