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: b6164fd5cd476d97627d1a0a98258b0a836f9266c1493a9a59f15f938625166b
Tx prefix hash: e95352c536c4d0efc177e2f8e59d311b066dfd3939cf6dfe573c4802815fc507
Tx public key: 5ab5a03f54fe89f7bab19c1f539c18b1a0d33ebbe24d8a1563228019d5702a09
| Timestamp: 1780816275 | Timestamp [UTC]: 2026-06-07 07:11:15 | Age [y:d:h:m:s]: 00:001:14:00:52 |
| Block: 7071 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 815 | RingCT/type: yes/0 |
| Extra: 015ab5a03f54fe89f7bab19c1f539c18b1a0d33ebbe24d8a1563228019d5702a09020900000001e49593ff00 | ||
1 output(s) for total of 34.713096676383 HMNY
| stealth address | amount | amount idx | tag |
| 00: 63f50378099dab1110b729235b1783121e3cb7cba65623ba72ead4bc12039404 | 34.713096676383 | 8719 of 0 | <35> |
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": 7131,
"vin": [ {
"gen": {
"height": 7071
}
}
],
"vout": [ {
"amount": 34713096676383,
"target": {
"tagged_key": {
"key": "63f50378099dab1110b729235b1783121e3cb7cba65623ba72ead4bc12039404",
"view_tag": "35"
}
}
}
],
"extra": [ 1, 90, 181, 160, 63, 84, 254, 137, 247, 186, 177, 156, 31, 83, 156, 24, 177, 160, 211, 62, 187, 226, 77, 138, 21, 99, 34, 128, 25, 213, 112, 42, 9, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}