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: dd5893903dd6ec5e8b3c3bb54fa54a471af39504b08ed097b856a612fcfc55e0
Tx prefix hash: 441061bc6253bcea24edc5ad09a05572ee1aa2beb532154a172e452da39292e9
Tx public key: f979a84a5fc867d0d21b528d753e65a162fc35b1b73b3a599daf2cc3ed867207
| Timestamp: 1779932335 | Timestamp [UTC]: 2026-05-28 01:38:55 | Age [y:d:h:m:s]: 00:011:23:57:02 |
| Block: 3409 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4477 | RingCT/type: yes/0 |
| Extra: 01f979a84a5fc867d0d21b528d753e65a162fc35b1b73b3a599daf2cc3ed86720702090000000226697be300 | ||
1 output(s) for total of 34.956406581444 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3146045d8dad9420405f6cd016d3217027d83a9b51b1f6a354a498fb46bbff47 | 34.956406581444 | 4124 of 0 | <07> |
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": 3469,
"vin": [ {
"gen": {
"height": 3409
}
}
],
"vout": [ {
"amount": 34956406581444,
"target": {
"tagged_key": {
"key": "3146045d8dad9420405f6cd016d3217027d83a9b51b1f6a354a498fb46bbff47",
"view_tag": "07"
}
}
}
],
"extra": [ 1, 249, 121, 168, 74, 95, 200, 103, 208, 210, 27, 82, 141, 117, 62, 101, 161, 98, 252, 53, 177, 183, 59, 58, 89, 157, 175, 44, 195, 237, 134, 114, 7, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}