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: b2d5a1d42c505328b107066eaf00d95f0e602beaf40abecf034001d587f718d9
Tx prefix hash: 19535d6bcb3fde497fc12e0964604357f48e44bd8aa9f9e8d65a0beb1a1f9eca
Tx public key: 36d34d428b0d5ff13008c73a5af22db8388486b041c6d9ecc0c5f8ded2f6a74d
| Timestamp: 1780836073 | Timestamp [UTC]: 2026-06-07 12:41:13 | Age [y:d:h:m:s]: 00:001:12:54:44 |
| Block: 7408 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 478 | RingCT/type: yes/0 |
| Extra: 0136d34d428b0d5ff13008c73a5af22db8388486b041c6d9ecc0c5f8ded2f6a74d020900000001e49593ff00 | ||
1 output(s) for total of 34.690791062228 HMNY
| stealth address | amount | amount idx | tag |
| 00: 934eda7fda157c5a994816f60644af0f088e2a1b4dd2360c026c9b492593b04a | 34.690791062228 | 9122 of 0 | <18> |
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": 7468,
"vin": [ {
"gen": {
"height": 7408
}
}
],
"vout": [ {
"amount": 34690791062228,
"target": {
"tagged_key": {
"key": "934eda7fda157c5a994816f60644af0f088e2a1b4dd2360c026c9b492593b04a",
"view_tag": "18"
}
}
}
],
"extra": [ 1, 54, 211, 77, 66, 139, 13, 95, 241, 48, 8, 199, 58, 90, 242, 45, 184, 56, 132, 134, 176, 65, 198, 217, 236, 192, 197, 248, 222, 210, 246, 167, 77, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}