Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fcddad1d849cf82fbe2d0e0f5008976b62516d0335bbb9de367f2bcdfc86aae

Tx prefix hash: 768609a66daf722765664da5f6f2137462a44e8c31fca9e69818594eb81b221f
Tx public key: 6c08b61f12ad56eeceff7d393678634345a6b0d60ee7cc2f361891dbefb352ef
Timestamp: 1772903003 Timestamp [UTC]: 2026-03-07 17:03:23 Age [y:d:h:m:s]: 00:258:03:35:24
Block: 1492780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190142 RingCT/type: yes/0
Extra: 016c08b61f12ad56eeceff7d393678634345a6b0d60ee7cc2f361891dbefb352ef021100000009e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 533e8458753fee25797d7d4cd5afe2206c3e61f5a7d4d43b752fb0355efbbbe4 0.000600000000 1982332 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": 1492790, "vin": [ { "gen": { "height": 1492780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "533e8458753fee25797d7d4cd5afe2206c3e61f5a7d4d43b752fb0355efbbbe4" } } ], "extra": [ 1, 108, 8, 182, 31, 18, 173, 86, 238, 206, 255, 125, 57, 54, 120, 99, 67, 69, 166, 176, 214, 14, 231, 204, 47, 54, 24, 145, 219, 239, 179, 82, 239, 2, 17, 0, 0, 0, 9, 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: