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: f63bffc6b912d4040c430170db2ecf1d081a69a1863820668dd20d67e82d03aa
Tx prefix hash: 45087d3da311fe50bca1d9f0830acbaef6591d81d377023cabf986f76a4ba622
Tx public key: d3225021ea4855c1bf587cc915d772efe1be146f9e629e5c32bf3db33af593ca
| Timestamp: 1780695548 | Timestamp [UTC]: 2026-06-05 21:39:08 | Age [y:d:h:m:s]: 00:003:05:59:42 |
| Block: 5977 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1972 | RingCT/type: yes/0 |
| Extra: 01d3225021ea4855c1bf587cc915d772efe1be146f9e629e5c32bf3db33af593ca020900000002e49593ff00 | ||
1 output(s) for total of 34.785606085089 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9b9acb07fec2bb884b8bac5d0545a1ba43e0e13e35e50f30f6912bb1817a2f6e | 34.785606085089 | 7442 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": 6037,
"vin": [ {
"gen": {
"height": 5977
}
}
],
"vout": [ {
"amount": 34785606085089,
"target": {
"tagged_key": {
"key": "9b9acb07fec2bb884b8bac5d0545a1ba43e0e13e35e50f30f6912bb1817a2f6e",
"view_tag": "58"
}
}
}
],
"extra": [ 1, 211, 34, 80, 33, 234, 72, 85, 193, 191, 88, 124, 201, 21, 215, 114, 239, 225, 190, 20, 111, 158, 98, 158, 92, 50, 191, 61, 179, 58, 245, 147, 202, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}