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: 1256cacd09b32719ad44c4d1e6fdfb88f469300299bf1a8e8ee8537d9437056e
Tx prefix hash: 1b4a2e2d16c8661bc68d7a2a3737370cf4f086de0da27843309b1e3ad564d1a2
Tx public key: c4fdfd6aa27f3f8b98f0c56a3f36727b84f0983d096d3788635a0180107bef56
| Timestamp: 1779465245 | Timestamp [UTC]: 2026-05-22 15:54:05 | Age [y:d:h:m:s]: 00:017:10:55:43 |
| Block: 497 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7402 | RingCT/type: yes/0 |
| Extra: 01c4fdfd6aa27f3f8b98f0c56a3f36727b84f0983d096d3788635a0180107bef5602090000000293369e7d00 | ||
1 output(s) for total of 35.151101800747 HMNY
| stealth address | amount | amount idx | tag |
| 00: bde1eac4d31cba30cfdf998b241d4017402f7eed4748938e79ecaf06d1bda43a | 35.151101800747 | 501 of 0 | <ff> |
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": 557,
"vin": [ {
"gen": {
"height": 497
}
}
],
"vout": [ {
"amount": 35151101800747,
"target": {
"tagged_key": {
"key": "bde1eac4d31cba30cfdf998b241d4017402f7eed4748938e79ecaf06d1bda43a",
"view_tag": "ff"
}
}
}
],
"extra": [ 1, 196, 253, 253, 106, 162, 127, 63, 139, 152, 240, 197, 106, 63, 54, 114, 123, 132, 240, 152, 61, 9, 109, 55, 136, 99, 90, 1, 128, 16, 123, 239, 86, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}