Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a69c6e8a1578df4013fc5182cece0527ca601ed65540767bd2d809ed59ecfefa

Tx prefix hash: 7b02008a9e7a52d991c135fd7bacd7d721cecc7b87ba12297fda988d4b6d4241
Tx public key: ec5c4ece36c99c6f83ffb70b26a3fbcc7800c4dd06dda212cb58358895658931
Timestamp: 1772206540 Timestamp [UTC]: 2026-02-27 15:35:40 Age [y:d:h:m:s]: 00:266:13:39:34
Block: 1486999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196186 RingCT/type: yes/0
Extra: 01ec5c4ece36c99c6f83ffb70b26a3fbcc7800c4dd06dda212cb58358895658931021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 780764b6611f8768f4c8cb77da7459e425d789fa2d1766b3a9ebe6b2f8f72373 0.000600000000 1976459 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": 1487009, "vin": [ { "gen": { "height": 1486999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "780764b6611f8768f4c8cb77da7459e425d789fa2d1766b3a9ebe6b2f8f72373" } } ], "extra": [ 1, 236, 92, 78, 206, 54, 201, 156, 111, 131, 255, 183, 11, 38, 163, 251, 204, 120, 0, 196, 221, 6, 221, 162, 18, 203, 88, 53, 136, 149, 101, 137, 49, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: