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: 20c5b480e6e1e4883622e4005078b86abd3016df88446ac942e836c89318c0ce
Tx prefix hash: de2de1bcb5f41fbc395847e8699191440171c9be6ef5d1fdad4d905df901d599
Tx public key: b1dfa9144b2fd1a1c4322e4dd1587f1aa47ab339f31e02e976e0cac94f3b626e
| Timestamp: 1780807819 | Timestamp [UTC]: 2026-06-07 04:50:19 | Age [y:d:h:m:s]: 00:001:21:59:29 |
| Block: 6976 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 924 | RingCT/type: yes/0 |
| Extra: 01b1dfa9144b2fd1a1c4322e4dd1587f1aa47ab339f31e02e976e0cac94f3b626e020900000001e49593ff00 | ||
1 output(s) for total of 34.719387200141 HMNY
| stealth address | amount | amount idx | tag |
| 00: c4dc971ee83bac7b293f0879ba386b3490a8e75a4504f00b955ba1fe505a3b60 | 34.719387200141 | 8604 of 0 | <72> |
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": 7036,
"vin": [ {
"gen": {
"height": 6976
}
}
],
"vout": [ {
"amount": 34719387200141,
"target": {
"tagged_key": {
"key": "c4dc971ee83bac7b293f0879ba386b3490a8e75a4504f00b955ba1fe505a3b60",
"view_tag": "72"
}
}
}
],
"extra": [ 1, 177, 223, 169, 20, 75, 47, 209, 161, 196, 50, 46, 77, 209, 88, 127, 26, 164, 122, 179, 57, 243, 30, 2, 233, 118, 224, 202, 201, 79, 59, 98, 110, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}