For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 59498fdb656ac8a77d4a2f0edbe4ebfca682dcc361a18e6ca8735d611150026a
Tx prefix hash: 6b756573f7dd719f69632cc0f6237aa2966e7a5a210d6ac2987342cecd52924c
Tx public key: 6317725272dc9d1d7011b04a04c2dfb8172f57c5b6036e942a6e7aede6fac33b
| Timestamp: 1780741398 | Timestamp [UTC]: 2026-06-06 10:23:18 | Age [y:d:h:m:s]: 00:007:00:57:47 |
| Block: 6413 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2332 | RingCT/type: yes/0 |
| Extra: 016317725272dc9d1d7011b04a04c2dfb8172f57c5b6036e942a6e7aede6fac33b020900000002e49593ff00 | ||
1 output(s) for total of 34.756690233149 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3686b45761ab09cb3fb0f9ab4d46a328b0cd05c7e5ad09072bbda6e7adcde4f7 | 34.756690233149 | 7904 of 0 | <1d> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 6473,
"vin": [ {
"gen": {
"height": 6413
}
}
],
"vout": [ {
"amount": 34756690233149,
"target": {
"tagged_key": {
"key": "3686b45761ab09cb3fb0f9ab4d46a328b0cd05c7e5ad09072bbda6e7adcde4f7",
"view_tag": "1d"
}
}
}
],
"extra": [ 1, 99, 23, 114, 82, 114, 220, 157, 29, 112, 17, 176, 74, 4, 194, 223, 184, 23, 47, 87, 197, 182, 3, 110, 148, 42, 110, 122, 237, 230, 250, 195, 59, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}