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: b38e54b5e0bdc3f351dc385c5fd296ebd8b97f466f0ff87a75f93a63b04bb14e
Tx prefix hash: b7f54279c311b88b1c9d7e963bec2e408ef18f2f1770306eaebd201ef6431dcb
Tx public key: 03c3962c255aa9e058ab9d95e15bfbee8b58907d5f061586359aefa1fe4aaafe
| Timestamp: 1780687604 | Timestamp [UTC]: 2026-06-05 19:26:44 | Age [y:d:h:m:s]: 00:003:21:42:19 |
| Block: 5490 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3244 | RingCT/type: yes/0 |
| Extra: 0103c3962c255aa9e058ab9d95e15bfbee8b58907d5f061586359aefa1fe4aaafe020900000001e49593ff00 | ||
1 output(s) for total of 34.817932738852 HMNY
| stealth address | amount | amount idx | tag |
| 00: b6ea6ba2140aa3b5585e04f23473002c4d479357bf3dee9509537a994c4a4e8a | 34.817932738852 | 6929 of 0 | <d7> |
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": 5550,
"vin": [ {
"gen": {
"height": 5490
}
}
],
"vout": [ {
"amount": 34817932738852,
"target": {
"tagged_key": {
"key": "b6ea6ba2140aa3b5585e04f23473002c4d479357bf3dee9509537a994c4a4e8a",
"view_tag": "d7"
}
}
}
],
"extra": [ 1, 3, 195, 150, 44, 37, 90, 169, 224, 88, 171, 157, 149, 225, 91, 251, 238, 139, 88, 144, 125, 95, 6, 21, 134, 53, 154, 239, 161, 254, 74, 170, 254, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}