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: 1f53d4859cd8e31563ce6bb9722c92ed8b7604ae895fdfba9f1204bb90041bd1
Tx prefix hash: 6253b755760a8de4a1e0b9b06e2870529da662a9abe03e0512806a74c498b07a
Tx public key: c773efba005fee8a3da4a764718a488acbf41b93ca1f732cf0db24bb2fbabb8c
| Timestamp: 1780857079 | Timestamp [UTC]: 2026-06-07 18:31:19 | Age [y:d:h:m:s]: 00:001:02:40:48 |
| Block: 7583 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 303 | RingCT/type: yes/0 |
| Extra: 01c773efba005fee8a3da4a764718a488acbf41b93ca1f732cf0db24bb2fbabb8c020900000005e49593ff00 | ||
1 output(s) for total of 34.679213682720 HMNY
| stealth address | amount | amount idx | tag |
| 00: 695248b897a3c8d17a8f4985bc2f1b24e0b12828ddd5a36975410c25016129d9 | 34.679213682720 | 9367 of 0 | <11> |
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": 7643,
"vin": [ {
"gen": {
"height": 7583
}
}
],
"vout": [ {
"amount": 34679213682720,
"target": {
"tagged_key": {
"key": "695248b897a3c8d17a8f4985bc2f1b24e0b12828ddd5a36975410c25016129d9",
"view_tag": "11"
}
}
}
],
"extra": [ 1, 199, 115, 239, 186, 0, 95, 238, 138, 61, 164, 167, 100, 113, 138, 72, 138, 203, 244, 27, 147, 202, 31, 115, 44, 240, 219, 36, 187, 47, 186, 187, 140, 2, 9, 0, 0, 0, 5, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}