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: 92271b13834026d46e278aeb8cd53fa6202e678f58831b58c53d1fdb9ce00e97
Tx prefix hash: 8553a0100c2e2d2992df42af01ab9f91bdbf0d61ce609421e5c27af2c74576c3
Tx public key: 817c8e96d5a8a554044ff8754e4829aa0b6df8e77d4e10fff5220aaac9b5947d
| Timestamp: 1780731796 | Timestamp [UTC]: 2026-06-06 07:43:16 | Age [y:d:h:m:s]: 00:002:17:03:31 |
| Block: 6327 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1559 | RingCT/type: yes/0 |
| Extra: 01817c8e96d5a8a554044ff8754e4829aa0b6df8e77d4e10fff5220aaac9b5947d020900000002e49593ff00 | ||
1 output(s) for total of 34.762391915004 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7853575afdca0c1513289b5bd605cfb972d5db47d420a4e7f604e8952f19faca | 34.762391915004 | 7814 of 0 | <e3> |
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": 6387,
"vin": [ {
"gen": {
"height": 6327
}
}
],
"vout": [ {
"amount": 34762391915004,
"target": {
"tagged_key": {
"key": "7853575afdca0c1513289b5bd605cfb972d5db47d420a4e7f604e8952f19faca",
"view_tag": "e3"
}
}
}
],
"extra": [ 1, 129, 124, 142, 150, 213, 168, 165, 84, 4, 79, 248, 117, 78, 72, 41, 170, 11, 109, 248, 231, 125, 78, 16, 255, 245, 34, 10, 170, 201, 181, 148, 125, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}