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: 0bc1916697bc80473b4b2eafa6b73faf30c74462e9f2bd8e005d205e1ff4e3ac
Tx prefix hash: 7d12ce89161d57e0b085442fdbd99ba15a0e1292d76250edd24e1e457feb6e4d
Tx public key: 6dfd212b409689a5e757c8bafba4371dcb6b3b0656e5f3f1f6357616a363d1d8
| Timestamp: 1779763761 | Timestamp [UTC]: 2026-05-26 02:49:21 | Age [y:d:h:m:s]: 00:018:08:12:55 |
| Block: 1952 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6793 | RingCT/type: yes/0 |
| Extra: 016dfd212b409689a5e757c8bafba4371dcb6b3b0656e5f3f1f6357616a363d1d802090000000626697be300 | ||
1 output(s) for total of 35.057891878649 HMNY
| stealth address | amount | amount idx | tag |
| 00: f6cd34db3cd2b38e6dc3d5b4ac936731234f321994ae9035725003c3ff29904e | 35.057891878649 | 2212 of 0 | <57> |
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": 2012,
"vin": [ {
"gen": {
"height": 1952
}
}
],
"vout": [ {
"amount": 35057891878649,
"target": {
"tagged_key": {
"key": "f6cd34db3cd2b38e6dc3d5b4ac936731234f321994ae9035725003c3ff29904e",
"view_tag": "57"
}
}
}
],
"extra": [ 1, 109, 253, 33, 43, 64, 150, 137, 165, 231, 87, 200, 186, 251, 164, 55, 29, 203, 107, 59, 6, 86, 229, 243, 241, 246, 53, 118, 22, 163, 99, 209, 216, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}