Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e6d6e5d396d20e5e0bb13aaffe39aa237a21623e7722277d17545b24c5b4003

Tx prefix hash: d7c39ab318f854deeeb05f3ecfb70aa94ff9d10da097c83065b8ae733429c5b1
Tx public key: f4d2dd9adfcf533d0b58d9a0ab63d91f2304d6de01702828c4e9615381cecc49
Timestamp: 1706910392 Timestamp [UTC]: 2024-02-02 21:46:32 Age [y:d:h:m:s]: 02:098:14:49:46
Block: 949019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 582510 RingCT/type: yes/0
Extra: 01f4d2dd9adfcf533d0b58d9a0ab63d91f2304d6de01702828c4e9615381cecc490211000000030011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8b2cc0e3f78593d91a32c6b9a453eeea6fe547b55784afe600086ff6323a3939 0.000600000000 1407541 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": 949029, "vin": [ { "gen": { "height": 949019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b2cc0e3f78593d91a32c6b9a453eeea6fe547b55784afe600086ff6323a3939" } } ], "extra": [ 1, 244, 210, 221, 154, 223, 207, 83, 61, 11, 88, 217, 160, 171, 99, 217, 31, 35, 4, 214, 222, 1, 112, 40, 40, 196, 233, 97, 83, 129, 206, 204, 73, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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: