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: cf5e15c322b0556936e2d894e73c540984dc1a7180cd7d0e12a0a4c00fe51a6a
Tx prefix hash: 9f9598af725b280eefb0bc66a1f3efd3683744ec55572a57f3a8739dfcd682f3
Tx public key: 02bf05d897b1f6936a7304160cb8a03e2c190a6cd2bcc4b48b23d696785810f0
| Timestamp: 1779840100 | Timestamp [UTC]: 2026-05-27 00:01:40 | Age [y:d:h:m:s]: 00:013:01:34:17 |
| Block: 2377 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5509 | RingCT/type: yes/0 |
| Extra: 0102bf05d897b1f6936a7304160cb8a03e2c190a6cd2bcc4b48b23d696785810f002090000000126697be300 | ||
1 output(s) for total of 35.025282035593 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2f74ee9c9aee57339d00dc979ce3c11b2642d05bba7aacd08273c1aebdfacffd | 35.025282035593 | 2789 of 0 | <92> |
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": 2437,
"vin": [ {
"gen": {
"height": 2377
}
}
],
"vout": [ {
"amount": 35025282035593,
"target": {
"tagged_key": {
"key": "2f74ee9c9aee57339d00dc979ce3c11b2642d05bba7aacd08273c1aebdfacffd",
"view_tag": "92"
}
}
}
],
"extra": [ 1, 2, 191, 5, 216, 151, 177, 246, 147, 106, 115, 4, 22, 12, 184, 160, 62, 44, 25, 10, 108, 210, 188, 196, 180, 139, 35, 214, 150, 120, 88, 16, 240, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}