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: df2e7e3c0890394885ff3c4ad34367d774fc7df622933ff2b16874212fb0f4fd
Tx prefix hash: 3be48ffd3f1322da7d99c7b533a8663a7b0fae586afa19f6dad2b33b937e13da
Tx public key: 4517f3b3d7017e939f6ca78e32f86a0c70eb1c56213493ed8888be8fb8dcf07e
| Timestamp: 1780130245 | Timestamp [UTC]: 2026-05-30 08:37:25 | Age [y:d:h:m:s]: 00:009:19:55:37 |
| Block: 4934 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3093 | RingCT/type: yes/0 |
| Extra: 014517f3b3d7017e939f6ca78e32f86a0c70eb1c56213493ed8888be8fb8dcf07e02090000000226697be300 | ||
1 output(s) for total of 34.854876284317 HMNY
| stealth address | amount | amount idx | tag |
| 00: 11f441382b7238675f2c90c572d8807d79a0bd18eac15dcbf4f5acbe74c4c063 | 34.854876284317 | 6265 of 0 | <ce> |
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": 4994,
"vin": [ {
"gen": {
"height": 4934
}
}
],
"vout": [ {
"amount": 34854876284317,
"target": {
"tagged_key": {
"key": "11f441382b7238675f2c90c572d8807d79a0bd18eac15dcbf4f5acbe74c4c063",
"view_tag": "ce"
}
}
}
],
"extra": [ 1, 69, 23, 243, 179, 215, 1, 126, 147, 159, 108, 167, 142, 50, 248, 106, 12, 112, 235, 28, 86, 33, 52, 147, 237, 136, 136, 190, 143, 184, 220, 240, 126, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}