Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e517ef42e99e517bbb1098af372452ba1c82ba08e3d30abd5d53e0658a0d07e2

Tx prefix hash: 6169dd8f0bf5c587dd88337d21d7870f5722e9b95565872475d92dd3e7c8fc6e
Tx public key: 45e380f18c8853f14e5d18d4d550efe3b05b97aff918dd16cbaaadf1e109ce59
Timestamp: 1773507052 Timestamp [UTC]: 2026-03-14 16:50:52 Age [y:d:h:m:s]: 00:245:12:17:49
Block: 1497775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180881 RingCT/type: yes/0
Extra: 0145e380f18c8853f14e5d18d4d550efe3b05b97aff918dd16cbaaadf1e109ce59021100000008e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 16ed8fccedd7744c0c28c16053999c9d1a1b14bfe512f8792912fa5e9f91cd1b 0.000600000000 1987417 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": 1497785, "vin": [ { "gen": { "height": 1497775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16ed8fccedd7744c0c28c16053999c9d1a1b14bfe512f8792912fa5e9f91cd1b" } } ], "extra": [ 1, 69, 227, 128, 241, 140, 136, 83, 241, 78, 93, 24, 212, 213, 80, 239, 227, 176, 91, 151, 175, 249, 24, 221, 22, 203, 170, 173, 241, 225, 9, 206, 89, 2, 17, 0, 0, 0, 8, 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: