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: 3f0cc10356c840f43330bef5f736fcace7d0c230f236d42acb0653c198d88b84
Tx prefix hash: bed7d8b9f935be6ed4f37b10ed7aaafbf196a367a07cd1778e43117aa5f48af4
Tx public key: 1129aa038bfa38144cc76e83d34f9317f0108900d8b6d42f13a1851c7a68f8cf
| Timestamp: 1779455544 | Timestamp [UTC]: 2026-05-22 13:12:24 | Age [y:d:h:m:s]: 00:025:19:09:55 |
| Block: 378 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8367 | RingCT/type: yes/0 |
| Extra: 011129aa038bfa38144cc76e83d34f9317f0108900d8b6d42f13a1851c7a68f8cf02090000000493369e7d00 | ||
1 output(s) for total of 35.159081117183 HMNY
| stealth address | amount | amount idx | tag |
| 00: 461916d1aadd52255b20f79b5d1cc873196195f6d44a724077b3e624a6964d1a | 35.159081117183 | 376 of 0 | <3f> |
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": 438,
"vin": [ {
"gen": {
"height": 378
}
}
],
"vout": [ {
"amount": 35159081117183,
"target": {
"tagged_key": {
"key": "461916d1aadd52255b20f79b5d1cc873196195f6d44a724077b3e624a6964d1a",
"view_tag": "3f"
}
}
}
],
"extra": [ 1, 17, 41, 170, 3, 139, 250, 56, 20, 76, 199, 110, 131, 211, 79, 147, 23, 240, 16, 137, 0, 216, 182, 212, 47, 19, 161, 133, 28, 122, 104, 248, 207, 2, 9, 0, 0, 0, 4, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}