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: 2c79050969b3fb84738673106cf5b8cd14d602370b579405453c5d0173d5f233
Tx prefix hash: c7536c59e17def4356243fef379d1a492e2c2aaac66a5f6fd2e896665434532b
Tx public key: ad21fed500643796c8587ed58908c723553ec21e3f33d13eae46fb9d6af95956
| Timestamp: 1780017338 | Timestamp [UTC]: 2026-05-29 01:15:38 | Age [y:d:h:m:s]: 00:010:22:03:15 |
| Block: 4124 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3762 | RingCT/type: yes/0 |
| Extra: 01ad21fed500643796c8587ed58908c723553ec21e3f33d13eae46fb9d6af9595602090000000126697be300 | ||
1 output(s) for total of 34.908767078857 HMNY
| stealth address | amount | amount idx | tag |
| 00: 51f668e4a8d38fef1707363ae3795a098653042e2bb768f14c43d95d522932d0 | 34.908767078857 | 5147 of 0 | <42> |
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": 4184,
"vin": [ {
"gen": {
"height": 4124
}
}
],
"vout": [ {
"amount": 34908767078857,
"target": {
"tagged_key": {
"key": "51f668e4a8d38fef1707363ae3795a098653042e2bb768f14c43d95d522932d0",
"view_tag": "42"
}
}
}
],
"extra": [ 1, 173, 33, 254, 213, 0, 100, 55, 150, 200, 88, 126, 213, 137, 8, 199, 35, 85, 62, 194, 30, 63, 51, 209, 62, 174, 70, 251, 157, 106, 249, 89, 86, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}