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: b875be6ec34ebe6b13620a608bfb959f0606fc65700c0c8cf378c339244a53c8
Tx prefix hash: 6e31542c6ec8cf5e393047694e4979eadec82f691236a424b7826e449e462a1c
Tx public key: 6e05760be2c31bdfd4ae646554fc721c7e4d7d66dfa978379a0d0940e71db45c
| Timestamp: 1780322689 | Timestamp [UTC]: 2026-06-01 14:04:49 | Age [y:d:h:m:s]: 00:013:18:14:46 |
| Block: 5007 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3738 | RingCT/type: yes/0 |
| Extra: 016e05760be2c31bdfd4ae646554fc721c7e4d7d66dfa978379a0d0940e71db45c02090000001426697be300 | ||
1 output(s) for total of 34.850023548290 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0045e0bef1173037cfabe1a2a11db4ca904e0e45f5518989312690bcefeb692d | 34.850023548290 | 6380 of 0 | <38> |
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": 5067,
"vin": [ {
"gen": {
"height": 5007
}
}
],
"vout": [ {
"amount": 34850023548290,
"target": {
"tagged_key": {
"key": "0045e0bef1173037cfabe1a2a11db4ca904e0e45f5518989312690bcefeb692d",
"view_tag": "38"
}
}
}
],
"extra": [ 1, 110, 5, 118, 11, 226, 195, 27, 223, 212, 174, 100, 101, 84, 252, 114, 28, 126, 77, 125, 102, 223, 169, 120, 55, 154, 13, 9, 64, 231, 29, 180, 92, 2, 9, 0, 0, 0, 20, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}