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: df73c5ed27e1df6525fccc149a07ea1d816a1eec5ade80a85aa5ff542a5b991f
Tx prefix hash: 2a99ce83e37d30152f84c6df476efc2fcf1106216d08c8763da4f51ffc606c7a
Tx public key: 5ea1d1b1fd9746e45ede728c4b593583a23950a17b08e9268ea3c49fa79bde65
| Timestamp: 1780740654 | Timestamp [UTC]: 2026-06-06 10:10:54 | Age [y:d:h:m:s]: 00:010:22:11:25 |
| Block: 6407 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2338 | RingCT/type: yes/0 |
| Extra: 015ea1d1b1fd9746e45ede728c4b593583a23950a17b08e9268ea3c49fa79bde65020900000005e49593ff00 | ||
1 output(s) for total of 34.757087994558 HMNY
| stealth address | amount | amount idx | tag |
| 00: 425329e408b0f371de74d40697febd871bb4cf0c9f33b8ec1f7d39446436e069 | 34.757087994558 | 7898 of 0 | <51> |
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": 6467,
"vin": [ {
"gen": {
"height": 6407
}
}
],
"vout": [ {
"amount": 34757087994558,
"target": {
"tagged_key": {
"key": "425329e408b0f371de74d40697febd871bb4cf0c9f33b8ec1f7d39446436e069",
"view_tag": "51"
}
}
}
],
"extra": [ 1, 94, 161, 209, 177, 253, 151, 70, 228, 94, 222, 114, 140, 75, 89, 53, 131, 162, 57, 80, 161, 123, 8, 233, 38, 142, 163, 196, 159, 167, 155, 222, 101, 2, 9, 0, 0, 0, 5, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}