Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e21984778f1ee207d3cb89f4c7b54ecb958b7001af045ff288c3d42f5fcf22d

Tx prefix hash: ef53200d78b60237b9103eaf4712b349f0f29db95339fd8eefc552022fafb759
Tx public key: 9ad52909a51a6c981f7900970cef7be9500fadaa93537c3a7ade24591361aa1b
Timestamp: 1741966752 Timestamp [UTC]: 2025-03-14 15:39:12 Age [y:d:h:m:s]: 01:057:18:25:24
Block: 1239216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292313 RingCT/type: yes/0
Extra: 019ad52909a51a6c981f7900970cef7be9500fadaa93537c3a7ade24591361aa1b0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4a707c4a41a2abc3150fef03fa022feaa5b3689ea7d157044381d8acbe578c94 0.000600000000 1726181 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": 1239226, "vin": [ { "gen": { "height": 1239216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a707c4a41a2abc3150fef03fa022feaa5b3689ea7d157044381d8acbe578c94" } } ], "extra": [ 1, 154, 213, 41, 9, 165, 26, 108, 152, 31, 121, 0, 151, 12, 239, 123, 233, 80, 15, 173, 170, 147, 83, 124, 58, 122, 222, 36, 89, 19, 97, 170, 27, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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: