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: ed19c63eb4d5c475bd7b1fee904e2ce701d5e65e581817d090ab47d9bcc89f5f
Tx prefix hash: fafd6b908bd5ca9eb51ddbfbe9e29518c278d0a49614941b0e82a05ad61d2eab
Tx public key: e9657e2491be37ae2bd808d21ae6d2efb3c05a1278f37e33e10028fcf7c6ffc4
| Timestamp: 1780972414 | Timestamp [UTC]: 2026-06-09 02:33:34 | Age [y:d:h:m:s]: 00:000:04:19:05 |
| Block: 7890 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 287 | RingCT/type: yes/0 |
| Extra: 01e9657e2491be37ae2bd808d21ae6d2efb3c05a1278f37e33e10028fcf7c6ffc4020900000002e49593ff00 | ||
1 output(s) for total of 34.658912984840 HMNY
| stealth address | amount | amount idx | tag |
| 00: dbf0a8dc2ba9a1d9b91294cc2a7545a1949d1dc0f43b7f7286e90b03b8b4ce2a | 34.658912984840 | 9784 of 0 | <4e> |
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": 7950,
"vin": [ {
"gen": {
"height": 7890
}
}
],
"vout": [ {
"amount": 34658912984840,
"target": {
"tagged_key": {
"key": "dbf0a8dc2ba9a1d9b91294cc2a7545a1949d1dc0f43b7f7286e90b03b8b4ce2a",
"view_tag": "4e"
}
}
}
],
"extra": [ 1, 233, 101, 126, 36, 145, 190, 55, 174, 43, 216, 8, 210, 26, 230, 210, 239, 179, 192, 90, 18, 120, 243, 126, 51, 225, 0, 40, 252, 247, 198, 255, 196, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}