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: 6ad83a5fb48535f4b3ca3715509b976e5238e63e7b972e3ea62e4b028029ca00
Tx prefix hash: 099fc36d86df66c1476785b7de2b16b28dd8351a8cbde601d057ab387f7076d3
Tx public key: de3c1874b7dca46bc6f1f66b3c5370ac7640b5c74766e1dc3bfc69e788dfb028
| Timestamp: 1779449913 | Timestamp [UTC]: 2026-05-22 11:38:33 | Age [y:d:h:m:s]: 00:017:13:57:24 |
| Block: 311 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7575 | RingCT/type: yes/0 |
| Extra: 01de3c1874b7dca46bc6f1f66b3c5370ac7640b5c74766e1dc3bfc69e788dfb0280209000000064438f87f00 | ||
1 output(s) for total of 35.163574470465 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6a80219e19fcb15bb5a734079d87ffb0414582daf3e8732772bb5a0e52c16bba | 35.163574470465 | 307 of 0 | <35> |
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": 371,
"vin": [ {
"gen": {
"height": 311
}
}
],
"vout": [ {
"amount": 35163574470465,
"target": {
"tagged_key": {
"key": "6a80219e19fcb15bb5a734079d87ffb0414582daf3e8732772bb5a0e52c16bba",
"view_tag": "35"
}
}
}
],
"extra": [ 1, 222, 60, 24, 116, 183, 220, 164, 107, 198, 241, 246, 107, 60, 83, 112, 172, 118, 64, 181, 199, 71, 102, 225, 220, 59, 252, 105, 231, 136, 223, 176, 40, 2, 9, 0, 0, 0, 6, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}