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: 38e3bdc8605f766a04bd80a061a4889a02c5f9334f6ee048079822397454578f
Tx prefix hash: 07451b5189ddcc6d6f8a09673e37199f44607a6f7d9ef3c99baa1e26bd61bcf9
Tx public key: fe953e70df83b2b9154a162edd21d6c8a15b81640a65211e3b74bc48400db128
| Timestamp: 1780818376 | Timestamp [UTC]: 2026-06-07 07:46:16 | Age [y:d:h:m:s]: 00:001:19:03:32 |
| Block: 7109 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 790 | RingCT/type: yes/0 |
| Extra: 01fe953e70df83b2b9154a162edd21d6c8a15b81640a65211e3b74bc48400db128020900000002e49593ff00 | ||
1 output(s) for total of 34.710580786015 HMNY
| stealth address | amount | amount idx | tag |
| 00: bbfb68d41c611ee987bfb81c7d32b07d2ba495429d4365fe984b91627a44999c | 34.710580786015 | 8763 of 0 | <ad> |
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": 7169,
"vin": [ {
"gen": {
"height": 7109
}
}
],
"vout": [ {
"amount": 34710580786015,
"target": {
"tagged_key": {
"key": "bbfb68d41c611ee987bfb81c7d32b07d2ba495429d4365fe984b91627a44999c",
"view_tag": "ad"
}
}
}
],
"extra": [ 1, 254, 149, 62, 112, 223, 131, 178, 185, 21, 74, 22, 46, 221, 33, 214, 200, 161, 91, 129, 100, 10, 101, 33, 30, 59, 116, 188, 72, 64, 13, 177, 40, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}