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: b1c845ffcaeb71c976b890186384680dd18b625cdef2d26913f9e3f0e92774f4
Tx prefix hash: 3d1d16c42ff2c39a6c48305d6acb607218dc87b267ca1e64b3a9cded5214f2fe
Tx public key: c9e682796acd522cfd72f76c97d32e64a60bc53f92a2d7f16003ab50790b697e
| Timestamp: 1779896276 | Timestamp [UTC]: 2026-05-27 15:37:56 | Age [y:d:h:m:s]: 00:012:09:58:01 |
| Block: 3106 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4780 | RingCT/type: yes/0 |
| Extra: 01c9e682796acd522cfd72f76c97d32e64a60bc53f92a2d7f16003ab50790b697e02090000000126697be300 | ||
1 output(s) for total of 34.976614678005 HMNY
| stealth address | amount | amount idx | tag |
| 00: 708ea517fbfa5b9e15ea620a154edb08a1493e2a512ee5fcdb1c771b7c0f72c7 | 34.976614678005 | 3704 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": 3166,
"vin": [ {
"gen": {
"height": 3106
}
}
],
"vout": [ {
"amount": 34976614678005,
"target": {
"tagged_key": {
"key": "708ea517fbfa5b9e15ea620a154edb08a1493e2a512ee5fcdb1c771b7c0f72c7",
"view_tag": "53"
}
}
}
],
"extra": [ 1, 201, 230, 130, 121, 106, 205, 82, 44, 253, 114, 247, 108, 151, 211, 46, 100, 166, 11, 197, 63, 146, 162, 215, 241, 96, 3, 171, 80, 121, 11, 105, 126, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}