Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa9750257618e46a75c0a7fd3e81d83fc9548964cd48364bbacaca33d7c86f6f

Tx prefix hash: 813c458dd6489268c169374be3a347a72fee2ea69c25ea31b17277b362e66114
Tx public key: 8a665bf9f872d5123e782773b72590e7867aaa75c9cd4e53873f2211df0e50e0
Timestamp: 1773275665 Timestamp [UTC]: 2026-03-12 00:34:25 Age [y:d:h:m:s]: 00:252:05:35:40
Block: 1495857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185832 RingCT/type: yes/0
Extra: 018a665bf9f872d5123e782773b72590e7867aaa75c9cd4e53873f2211df0e50e0021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7478c827e11ae4fdbb089e765c4229fffb7c8632a5d65c704407731fed44729f 0.000600000000 1985471 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": 1495867, "vin": [ { "gen": { "height": 1495857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7478c827e11ae4fdbb089e765c4229fffb7c8632a5d65c704407731fed44729f" } } ], "extra": [ 1, 138, 102, 91, 249, 248, 114, 213, 18, 62, 120, 39, 115, 183, 37, 144, 231, 134, 122, 170, 117, 201, 205, 78, 83, 135, 63, 34, 17, 223, 14, 80, 224, 2, 17, 0, 0, 0, 4, 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: