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: fe06f5f0352c82e22013bdd0dbbd50bd5e2686d9cb2fe49d10a91583c0974423
Tx prefix hash: 57f6b1ad7a7e744e86130c9678bf8b0f8d9c58974c115c3c325190d4dc422d51
Tx public key: b0c4956792a5e914ec66fed024924d6d8c8bdb8c816c2d425f3ba3b493a1fd28
| Timestamp: 1779924765 | Timestamp [UTC]: 2026-05-27 23:32:45 | Age [y:d:h:m:s]: 00:020:08:32:36 |
| Block: 3371 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5374 | RingCT/type: yes/0 |
| Extra: 01b0c4956792a5e914ec66fed024924d6d8c8bdb8c816c2d425f3ba3b493a1fd2802090000000226697be300 | ||
1 output(s) for total of 34.961558689743 HMNY
| stealth address | amount | amount idx | tag |
| 00: e6c3fd20e83f3319f68ef1dabe5c47fabd92f06f3ac8e76aa96468eeab95d16b | 34.961558689743 | 4064 of 0 | <d0> |
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": 3431,
"vin": [ {
"gen": {
"height": 3371
}
}
],
"vout": [ {
"amount": 34961558689743,
"target": {
"tagged_key": {
"key": "e6c3fd20e83f3319f68ef1dabe5c47fabd92f06f3ac8e76aa96468eeab95d16b",
"view_tag": "d0"
}
}
}
],
"extra": [ 1, 176, 196, 149, 103, 146, 165, 233, 20, 236, 102, 254, 208, 36, 146, 77, 109, 140, 139, 219, 140, 129, 108, 45, 66, 95, 59, 163, 180, 147, 161, 253, 40, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}