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: 0f0b4facea6d1b30413be31e3229d92bae695165a9209d008a560ca80a4bd88c
Tx prefix hash: ebfd0253d8121e7b413c3db618c59a332b488c9ce8ffb693d251d22e5ccaf85f
Tx public key: 2b0c6a4422721f60eef0f9d776aa3a585f646ce224dfd3b2bc9c9737f9574cf2
| Timestamp: 1780023169 | Timestamp [UTC]: 2026-05-29 02:52:49 | Age [y:d:h:m:s]: 00:010:22:43:08 |
| Block: 4154 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3732 | RingCT/type: yes/0 |
| Extra: 012b0c6a4422721f60eef0f9d776aa3a585f646ce224dfd3b2bc9c9737f9574cf202090000000426697be300 | ||
1 output(s) for total of 34.906769638425 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1236fa04e60bbd1e35c334716a99023afb053e6f4e0170ab902bdaa00770f1d6 | 34.906769638425 | 5185 of 0 | <2e> |
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": 4214,
"vin": [ {
"gen": {
"height": 4154
}
}
],
"vout": [ {
"amount": 34906769638425,
"target": {
"tagged_key": {
"key": "1236fa04e60bbd1e35c334716a99023afb053e6f4e0170ab902bdaa00770f1d6",
"view_tag": "2e"
}
}
}
],
"extra": [ 1, 43, 12, 106, 68, 34, 114, 31, 96, 238, 240, 249, 215, 118, 170, 58, 88, 95, 100, 108, 226, 36, 223, 211, 178, 188, 156, 151, 55, 249, 87, 76, 242, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}