Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa603840c20e1517c23d1faf884f4aa30edb38234f4b58eee670fdff7a0fc4ad

Tx prefix hash: 19926ce930c3989a8098b9a7d9980c00349be101403e6a976f258e22d6988ba4
Tx public key: 8b13f6e5271b7ac7bd4995e73dc81194943af4397fd4070099c89ae6a09e0cb2
Timestamp: 1774096269 Timestamp [UTC]: 2026-03-21 12:31:09 Age [y:d:h:m:s]: 00:240:22:31:13
Block: 1502631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177704 RingCT/type: yes/0
Extra: 018b13f6e5271b7ac7bd4995e73dc81194943af4397fd4070099c89ae6a09e0cb2021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0de78c1cfb0bf551d1d106ef90c93f9d5e7c520dc5115670f0080cf77c2f4060 0.000600000000 1992333 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": 1502641, "vin": [ { "gen": { "height": 1502631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0de78c1cfb0bf551d1d106ef90c93f9d5e7c520dc5115670f0080cf77c2f4060" } } ], "extra": [ 1, 139, 19, 246, 229, 39, 27, 122, 199, 189, 73, 149, 231, 61, 200, 17, 148, 148, 58, 244, 57, 127, 212, 7, 0, 153, 200, 154, 230, 160, 158, 12, 178, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: