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: 96a1540ac587d57f5a0e4127f85fa6b52d65f6df0751ee2c8a39406169e7d2a0
Tx prefix hash: 97646a14179ed6e2ef4e876d6fec366f4d7ccf1314810a13e916dc3164de0d6a
Tx public key: fed1ade2532c54dd4c4c0fa29b160c5f7135d94f6cce671f07c0eb4e3949d716
| Timestamp: 1780058785 | Timestamp [UTC]: 2026-05-29 12:46:25 | Age [y:d:h:m:s]: 00:010:15:46:37 |
| Block: 4490 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3536 | RingCT/type: yes/0 |
| Extra: 01fed1ade2532c54dd4c4c0fa29b160c5f7135d94f6cce671f07c0eb4e3949d71602090000000526697be300 | ||
1 output(s) for total of 34.884406112450 HMNY
| stealth address | amount | amount idx | tag |
| 00: 406628934f1836a6e1a21aeb863bfea79e10c646e5b05bd5760292fe159ee393 | 34.884406112450 | 5626 of 0 | <53> |
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": 4550,
"vin": [ {
"gen": {
"height": 4490
}
}
],
"vout": [ {
"amount": 34884406112450,
"target": {
"tagged_key": {
"key": "406628934f1836a6e1a21aeb863bfea79e10c646e5b05bd5760292fe159ee393",
"view_tag": "53"
}
}
}
],
"extra": [ 1, 254, 209, 173, 226, 83, 44, 84, 221, 76, 76, 15, 162, 155, 22, 12, 95, 113, 53, 217, 79, 108, 206, 103, 31, 7, 192, 235, 78, 57, 73, 215, 22, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}