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: c6d4b0bb6fb2bf00e82eb7c9d44069719cdae7dcb1cd4d66534be5f57721002b
Tx prefix hash: 149c87a4cf1c6d310688d3f9ee02cf6305545437f91a66c385251201b26656ba
Tx public key: 861c0e7fad7dd13079be159bdbd49b57e2e055db9da8d002735af44887373236
| Timestamp: 1780895910 | Timestamp [UTC]: 2026-06-08 05:18:30 | Age [y:d:h:m:s]: 00:009:02:43:15 |
| Block: 7765 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 980 | RingCT/type: yes/0 |
| Extra: 01861c0e7fad7dd13079be159bdbd49b57e2e055db9da8d002735af448873732360209000000024a728a4c00 | ||
1 output(s) for total of 34.667177306654 HMNY
| stealth address | amount | amount idx | tag |
| 00: afac52dc48438f04b40382fc412c7c6f49c28cb51a2bba7a8efb50ed710574e5 | 34.667177306654 | 9617 of 0 | <ae> |
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": 7825,
"vin": [ {
"gen": {
"height": 7765
}
}
],
"vout": [ {
"amount": 34667177306654,
"target": {
"tagged_key": {
"key": "afac52dc48438f04b40382fc412c7c6f49c28cb51a2bba7a8efb50ed710574e5",
"view_tag": "ae"
}
}
}
],
"extra": [ 1, 134, 28, 14, 127, 173, 125, 209, 48, 121, 190, 21, 155, 219, 212, 155, 87, 226, 224, 85, 219, 157, 168, 208, 2, 115, 90, 244, 72, 135, 55, 50, 54, 2, 9, 0, 0, 0, 2, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}