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: d22b64a80f505bafde2bf9af117ab18f1bc44bbc3a5c9109690475af220bf598
Tx prefix hash: ec5b918993c3d6bfe55b9c81674a3d4a424be32ab29a5ad26b06c16bb353961e
Tx public key: a54d834f93350a67bf6c9d0598bccfbda4390308ddc7cd6aabe6b65ec84f5ada
| Timestamp: 1780739480 | Timestamp [UTC]: 2026-06-06 09:51:20 | Age [y:d:h:m:s]: 00:002:15:44:37 |
| Block: 6397 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1489 | RingCT/type: yes/0 |
| Extra: 01a54d834f93350a67bf6c9d0598bccfbda4390308ddc7cd6aabe6b65ec84f5ada020900000001e49593ff00 | ||
1 output(s) for total of 34.757750940355 HMNY
| stealth address | amount | amount idx | tag |
| 00: 39e4da3936d6d489b8e5bdd38a0ab06dfd9ddcda35dae650bb62ea1658e9f7bf | 34.757750940355 | 7888 of 0 | <80> |
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": 6457,
"vin": [ {
"gen": {
"height": 6397
}
}
],
"vout": [ {
"amount": 34757750940355,
"target": {
"tagged_key": {
"key": "39e4da3936d6d489b8e5bdd38a0ab06dfd9ddcda35dae650bb62ea1658e9f7bf",
"view_tag": "80"
}
}
}
],
"extra": [ 1, 165, 77, 131, 79, 147, 53, 10, 103, 191, 108, 157, 5, 152, 188, 207, 189, 164, 57, 3, 8, 221, 199, 205, 106, 171, 230, 182, 94, 200, 79, 90, 218, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}