Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5168335f325c86ee4db67a5e0fea24c8e907042fd8f845a4e16ea7ff7ab321f3

Tx prefix hash: a5fbcb4ad3ebc84c19521e1d6bcb484f4093b593f05af96d4568daa78c67957a
Tx public key: 6adde9a866c6abdc54f6e97e5d2942844c2453540c522f2aca19c6f9ee6350ef
Timestamp: 1773182860 Timestamp [UTC]: 2026-03-10 22:47:40 Age [y:d:h:m:s]: 00:252:18:32:43
Block: 1495086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186187 RingCT/type: yes/0
Extra: 016adde9a866c6abdc54f6e97e5d2942844c2453540c522f2aca19c6f9ee6350ef021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 967c7951f47e2addc92cf5f2a5d9953bcddcde35f7304d5095127d5f15627571 0.000600000000 1984694 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": 1495096, "vin": [ { "gen": { "height": 1495086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "967c7951f47e2addc92cf5f2a5d9953bcddcde35f7304d5095127d5f15627571" } } ], "extra": [ 1, 106, 221, 233, 168, 102, 198, 171, 220, 84, 246, 233, 126, 93, 41, 66, 132, 76, 36, 83, 84, 12, 82, 47, 42, 202, 25, 198, 249, 238, 99, 80, 239, 2, 17, 0, 0, 0, 1, 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: