Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b7f50583502cf75aa7fe8d7b726eae75a540e9028bba16964b7c406208d8f14

Tx prefix hash: 27728fb7a8576a89d8654458dd0532f0e0193e90ac68befaa784357076ff7568
Tx public key: 6a03c34733caff58300da36b0240be9d9719ab32a18cc8f2ac2af3ee75bd5c09
Timestamp: 1772886181 Timestamp [UTC]: 2026-03-07 12:23:01 Age [y:d:h:m:s]: 00:259:20:25:52
Block: 1492643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190851 RingCT/type: yes/0
Extra: 016a03c34733caff58300da36b0240be9d9719ab32a18cc8f2ac2af3ee75bd5c09021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e529e794b71746c10e0defb1059875f24c4456197d1f472ea86da681b9f3c412 0.000600000000 1982191 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": 1492653, "vin": [ { "gen": { "height": 1492643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e529e794b71746c10e0defb1059875f24c4456197d1f472ea86da681b9f3c412" } } ], "extra": [ 1, 106, 3, 195, 71, 51, 202, 255, 88, 48, 13, 163, 107, 2, 64, 190, 157, 151, 25, 171, 50, 161, 140, 200, 242, 172, 42, 243, 238, 117, 189, 92, 9, 2, 17, 0, 0, 0, 4, 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: