Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af6151c7cacf7b447066e0a3e29164a992d5bc98dbfe2650ae6166ee7944f779

Tx prefix hash: 39f2feecae99b35b1ab581778b9701055eb259ab2a52077dca0a24b0a4057db8
Tx public key: fc48deced3f0cab0fc62636d6a579dc2088431b4aecd71fc95b95174ee1b53f2
Timestamp: 1761137987 Timestamp [UTC]: 2025-10-22 12:59:47 Age [y:d:h:m:s]: 01:028:17:42:16
Block: 1395505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286977 RingCT/type: yes/0
Extra: 01fc48deced3f0cab0fc62636d6a579dc2088431b4aecd71fc95b95174ee1b53f20211000000015dfbbe2a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 27eeb025db643c315e59b93c1c9d2bb2889090c0c21bf7c7fb31af544fa890ea 0.000600000000 1883782 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": 1395515, "vin": [ { "gen": { "height": 1395505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27eeb025db643c315e59b93c1c9d2bb2889090c0c21bf7c7fb31af544fa890ea" } } ], "extra": [ 1, 252, 72, 222, 206, 211, 240, 202, 176, 252, 98, 99, 109, 106, 87, 157, 194, 8, 132, 49, 180, 174, 205, 113, 252, 149, 185, 81, 116, 238, 27, 83, 242, 2, 17, 0, 0, 0, 1, 93, 251, 190, 42, 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: