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: 8f4fa802a5c9731e825f73eb248a3e2ce9a2ea41fdf6994cedb0d7931f7d5d1e
Tx prefix hash: 14a46aeb7ba0c6e8f6f219fe87188e55a3862a3f1a4ff678f603784e1a6ebfd2
Tx public key: 0310f9c021d60a8f348f498f0888b4ea13945a34855f3eb9a4e2d08bd96a137d
| Timestamp: 1780136723 | Timestamp [UTC]: 2026-05-30 10:25:23 | Age [y:d:h:m:s]: 00:009:18:07:39 |
| Block: 4968 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3057 | RingCT/type: yes/0 |
| Extra: 010310f9c021d60a8f348f498f0888b4ea13945a34855f3eb9a4e2d08bd96a137d02090000000226697be300 | ||
1 output(s) for total of 34.852616021830 HMNY
| stealth address | amount | amount idx | tag |
| 00: f04721e7f8002e07c26ecc0f0fe83321b6a795571d6a57f065628a2f68cb7671 | 34.852616021830 | 6319 of 0 | <1c> |
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": 5028,
"vin": [ {
"gen": {
"height": 4968
}
}
],
"vout": [ {
"amount": 34852616021830,
"target": {
"tagged_key": {
"key": "f04721e7f8002e07c26ecc0f0fe83321b6a795571d6a57f065628a2f68cb7671",
"view_tag": "1c"
}
}
}
],
"extra": [ 1, 3, 16, 249, 192, 33, 214, 10, 143, 52, 143, 73, 143, 8, 136, 180, 234, 19, 148, 90, 52, 133, 95, 62, 185, 164, 226, 208, 139, 217, 106, 19, 125, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}