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: 9681712be0c6b646d566ad4bc19d59d6d3cdaa8fed41dffc6c118348b769ddeb
Tx prefix hash: 0b613b0f7f1f21b1ba7a9b1687a018e515b2d2ddd56e66e29c6a15177b366402
Tx public key: def0d9d3f0734e69a436a0c4c418755340ceba93f80a28fc3e7a801daf763c02
| Timestamp: 1780831122 | Timestamp [UTC]: 2026-06-07 11:18:42 | Age [y:d:h:m:s]: 00:005:23:43:34 |
| Block: 7342 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1403 | RingCT/type: yes/0 |
| Extra: 01def0d9d3f0734e69a436a0c4c418755340ceba93f80a28fc3e7a801daf763c02020900000001e49593ff00 | ||
1 output(s) for total of 34.695158391849 HMNY
| stealth address | amount | amount idx | tag |
| 00: 77d1291e475e50c9e2a328c8055461c8b6f3e6f8a356285856118131617a6fab | 34.695158391849 | 9038 of 0 | <13> |
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": 7402,
"vin": [ {
"gen": {
"height": 7342
}
}
],
"vout": [ {
"amount": 34695158391849,
"target": {
"tagged_key": {
"key": "77d1291e475e50c9e2a328c8055461c8b6f3e6f8a356285856118131617a6fab",
"view_tag": "13"
}
}
}
],
"extra": [ 1, 222, 240, 217, 211, 240, 115, 78, 105, 164, 54, 160, 196, 196, 24, 117, 83, 64, 206, 186, 147, 248, 10, 40, 252, 62, 122, 128, 29, 175, 118, 60, 2, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}