Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc5e83d8f543f3e01ea131a49e507cb89247a55999794c5d51bfc3ed6e4cbb6c

Tx prefix hash: 56955d73fd55115d8f3355d71fdda54dbdeb27c533b91422d7eac7bc943ab2a4
Tx public key: 00703af23fcf67d0572354abb6cc8c18b1c04ddbb9698a711f661632dc9df9e3
Timestamp: 1761353270 Timestamp [UTC]: 2025-10-25 00:47:50 Age [y:d:h:m:s]: 00:205:10:02:00
Block: 1397289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139314 RingCT/type: yes/0
Extra: 0100703af23fcf67d0572354abb6cc8c18b1c04ddbb9698a711f661632dc9df9e3021100000001d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 36feb906a8dce1df17c6d5ddb1992b75d21e3d284a518485a4f9518c23f1dff7 0.000600000000 1885580 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": 1397299, "vin": [ { "gen": { "height": 1397289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36feb906a8dce1df17c6d5ddb1992b75d21e3d284a518485a4f9518c23f1dff7" } } ], "extra": [ 1, 0, 112, 58, 242, 63, 207, 103, 208, 87, 35, 84, 171, 182, 204, 140, 24, 177, 192, 77, 219, 185, 105, 138, 113, 31, 102, 22, 50, 220, 157, 249, 227, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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: