Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ba4aec12c557263dffcd8c9b98de7a9c734dbcc0055bb433a7f989d36023915

Tx prefix hash: 169d83170c39d2ebe64a96c765f8d040cc02f4029ff4479878f072f3360ba4f1
Tx public key: 78fa89ca4775ba785a49e0f8e2929ab2855bd36553b8b0213d11091a0b062011
Timestamp: 1772650332 Timestamp [UTC]: 2026-03-04 18:52:12 Age [y:d:h:m:s]: 00:261:01:00:46
Block: 1490686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192221 RingCT/type: yes/0
Extra: 0178fa89ca4775ba785a49e0f8e2929ab2855bd36553b8b0213d11091a0b062011021100000010e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 21b3cec8433a9d3f10ea1d2e578eef1ee1f75ba4ec3e18c4f1e9fa2829b364e8 0.000600000000 1980194 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": 1490696, "vin": [ { "gen": { "height": 1490686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21b3cec8433a9d3f10ea1d2e578eef1ee1f75ba4ec3e18c4f1e9fa2829b364e8" } } ], "extra": [ 1, 120, 250, 137, 202, 71, 117, 186, 120, 90, 73, 224, 248, 226, 146, 154, 178, 133, 91, 211, 101, 83, 184, 176, 33, 61, 17, 9, 26, 11, 6, 32, 17, 2, 17, 0, 0, 0, 16, 228, 245, 25, 63, 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: