Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a69d9db0d6b370105ab8ee3b12f68f6bb9bbbe9a2a8687ff0b830e9dd65ef631

Tx prefix hash: d96452f261815db94c4b969eb85851c4b54282d42649c5b91983db81687d9ab6
Tx public key: 835eeb3dcc2e6a2a2cc46b2d02e8474980b4491aa878e34a62d8069873f1041c
Timestamp: 1748189603 Timestamp [UTC]: 2025-05-25 16:13:23 Age [y:d:h:m:s]: 01:180:15:46:02
Block: 1290731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392763 RingCT/type: yes/0
Extra: 01835eeb3dcc2e6a2a2cc46b2d02e8474980b4491aa878e34a62d8069873f1041c0211000000071f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: df5563a1c48e54db9cc9adf40504d3cf3cee3adaaa521b9b0f41bc309de53a13 0.000600000000 1778202 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": 1290741, "vin": [ { "gen": { "height": 1290731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df5563a1c48e54db9cc9adf40504d3cf3cee3adaaa521b9b0f41bc309de53a13" } } ], "extra": [ 1, 131, 94, 235, 61, 204, 46, 106, 42, 44, 196, 107, 45, 2, 232, 71, 73, 128, 180, 73, 26, 168, 120, 227, 74, 98, 216, 6, 152, 115, 241, 4, 28, 2, 17, 0, 0, 0, 7, 31, 144, 81, 122, 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: