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: 330ac8f64acc6fcb1c1137620b346ca0ce738139b7c46aecf34d9879981682f1
Tx prefix hash: a248b7958b92891e162ba6314525651484c5ae85bf893efac5f581f580668c8f
Tx public key: eb4f56bd9938d117cf3b11613498639cce6c1a3f079b5ace7cedec992672f5c4
| Timestamp: 1780761973 | Timestamp [UTC]: 2026-06-06 16:06:13 | Age [y:d:h:m:s]: 00:002:11:44:45 |
| Block: 6582 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1384 | RingCT/type: yes/0 |
| Extra: 01eb4f56bd9938d117cf3b11613498639cce6c1a3f079b5ace7cedec992672f5c4020900000001e49593ff00 | ||
1 output(s) for total of 34.745488489733 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8d3b8d1d0ed1901cbcb099dfb6875bc9116f0fe3e9299417178844018a0a8b8f | 34.745488489733 | 8106 of 0 | <96> |
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": 6642,
"vin": [ {
"gen": {
"height": 6582
}
}
],
"vout": [ {
"amount": 34745488489733,
"target": {
"tagged_key": {
"key": "8d3b8d1d0ed1901cbcb099dfb6875bc9116f0fe3e9299417178844018a0a8b8f",
"view_tag": "96"
}
}
}
],
"extra": [ 1, 235, 79, 86, 189, 153, 56, 209, 23, 207, 59, 17, 97, 52, 152, 99, 156, 206, 108, 26, 63, 7, 155, 90, 206, 124, 237, 236, 153, 38, 114, 245, 196, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}