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: add8a0b3d0c9373aa389031b43a82a83fb9a12f8294bde0ccb3452b0d7487464
Tx prefix hash: 6885f4d5147cf463e3b1600df2e87013fd2a0af985ac222a3b696e54336d3ae9
Tx public key: f3f576f9a56130a612001a29af77a2cefc9388fb577535dc3df5d0c3c4b2f4f6
| Timestamp: 1780842180 | Timestamp [UTC]: 2026-06-07 14:23:00 | Age [y:d:h:m:s]: 00:001:11:12:57 |
| Block: 7476 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 410 | RingCT/type: yes/0 |
| Extra: 01f3f576f9a56130a612001a29af77a2cefc9388fb577535dc3df5d0c3c4b2f4f6020900000002e49593ff00 | ||
1 output(s) for total of 34.686291964272 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3467cf40654c04da0493d382b5e6d9803ca6a1c0e8edabcb9862fa8642d29a19 | 34.686291964272 | 9210 of 0 | <29> |
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": 7536,
"vin": [ {
"gen": {
"height": 7476
}
}
],
"vout": [ {
"amount": 34686291964272,
"target": {
"tagged_key": {
"key": "3467cf40654c04da0493d382b5e6d9803ca6a1c0e8edabcb9862fa8642d29a19",
"view_tag": "29"
}
}
}
],
"extra": [ 1, 243, 245, 118, 249, 165, 97, 48, 166, 18, 0, 26, 41, 175, 119, 162, 206, 252, 147, 136, 251, 87, 117, 53, 220, 61, 245, 208, 195, 196, 178, 244, 246, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}