Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3eb9d1e90e137a1ef59ab561d103fa9a66d78b6fa26df6cd1c8353571dd09a16

Tx prefix hash: 659e0533511ea309d3d909d7455bddcdccfa5048e84ffaa1be25cb5bb3544ad8
Tx public key: 6c68cfd0e29140dc7b8556525dbfce43c157b55e5a012552fc43bd8d40636f14
Timestamp: 1772988117 Timestamp [UTC]: 2026-03-08 16:41:57 Age [y:d:h:m:s]: 00:251:04:40:10
Block: 1493487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184925 RingCT/type: yes/0
Extra: 016c68cfd0e29140dc7b8556525dbfce43c157b55e5a012552fc43bd8d40636f14021100000011f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 077b2f25672b7d5e455fadbc557e6abaccc6c887845968ed4b43078ec88c3d99 0.000600000000 1983047 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": 1493497, "vin": [ { "gen": { "height": 1493487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "077b2f25672b7d5e455fadbc557e6abaccc6c887845968ed4b43078ec88c3d99" } } ], "extra": [ 1, 108, 104, 207, 208, 226, 145, 64, 220, 123, 133, 86, 82, 93, 191, 206, 67, 193, 87, 181, 94, 90, 1, 37, 82, 252, 67, 189, 141, 64, 99, 111, 20, 2, 17, 0, 0, 0, 17, 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: