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: 25cb69ac03a6d87ca17cf3e13ae44ac71e290d08cefcbf12dfea4c006efc6075
Tx prefix hash: cc70262796ed8fe0c462189eb0b498b5ab2dd0f5d3131cf3f0cff1c716a91a23
Tx public key: 80d4f0f44a5dc546ec7c5805296dcbae5e72d9cf8ab83149ce6c6ae4bf7540a7
| Timestamp: 1780686120 | Timestamp [UTC]: 2026-06-05 19:02:00 | Age [y:d:h:m:s]: 00:007:16:00:16 |
| Block: 5412 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3333 | RingCT/type: yes/0 |
| Extra: 0180d4f0f44a5dc546ec7c5805296dcbae5e72d9cf8ab83149ce6c6ae4bf7540a7020900000001e49593ff00 | ||
1 output(s) for total of 34.823113104172 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6786b019f610d5dcebad7274f68a15c33931a72764ea193bb4b64a48bce718db | 34.823113104172 | 6849 of 0 | <f2> |
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": 5472,
"vin": [ {
"gen": {
"height": 5412
}
}
],
"vout": [ {
"amount": 34823113104172,
"target": {
"tagged_key": {
"key": "6786b019f610d5dcebad7274f68a15c33931a72764ea193bb4b64a48bce718db",
"view_tag": "f2"
}
}
}
],
"extra": [ 1, 128, 212, 240, 244, 74, 93, 197, 70, 236, 124, 88, 5, 41, 109, 203, 174, 94, 114, 217, 207, 138, 184, 49, 73, 206, 108, 106, 228, 191, 117, 64, 167, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}