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: 5109b109324b14f908ef34709fe3e65b31fc455b35effc5c54a1df99cfc6487e
Tx prefix hash: 0dddab8387ba63fa3d8025d56f3c8f2ab7c0eae5ca2c1c634842a42a95e8db54
Tx public key: 8d0e5e66aa73b33558e4d70f568c6bb71bb5e50e3bd60bf74d9789e6de3fe185
| Timestamp: 1780837347 | Timestamp [UTC]: 2026-06-07 13:02:27 | Age [y:d:h:m:s]: 00:001:12:33:30 |
| Block: 7425 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 461 | RingCT/type: yes/0 |
| Extra: 018d0e5e66aa73b33558e4d70f568c6bb71bb5e50e3bd60bf74d9789e6de3fe185020900000002e49593ff00 | ||
1 output(s) for total of 34.689666233032 HMNY
| stealth address | amount | amount idx | tag |
| 00: e64d744e911938602a55793443066d32766c018473d948279b2ff88988521b79 | 34.689666233032 | 9143 of 0 | <58> |
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": 7485,
"vin": [ {
"gen": {
"height": 7425
}
}
],
"vout": [ {
"amount": 34689666233032,
"target": {
"tagged_key": {
"key": "e64d744e911938602a55793443066d32766c018473d948279b2ff88988521b79",
"view_tag": "58"
}
}
}
],
"extra": [ 1, 141, 14, 94, 102, 170, 115, 179, 53, 88, 228, 215, 15, 86, 140, 107, 183, 27, 181, 229, 14, 59, 214, 11, 247, 77, 151, 137, 230, 222, 63, 225, 133, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}