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: 9c3832204510e7785f29b35a024ff3260c4c9418f7f5de56f72ab548f33836bf
Tx prefix hash: ec15cc09a38ac9cd794f8883fe7516543bda9b5ade75c94e2111e0385254885b
Tx public key: c9f6d4e088745368662c9d65d8f1a1caad4433a18a7f49de54e7240efb5f0dc2
| Timestamp: 1779764347 | Timestamp [UTC]: 2026-05-26 02:59:07 | Age [y:d:h:m:s]: 00:013:22:36:50 |
| Block: 1953 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5933 | RingCT/type: yes/0 |
| Extra: 01c9f6d4e088745368662c9d65d8f1a1caad4433a18a7f49de54e7240efb5f0dc202090000000526697be300 | ||
1 output(s) for total of 35.056231419049 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1b8a6350d966d7bead3440c85717f4ea21ae23477e0e51b357a0e6f6806cbb0d | 35.056231419049 | 2215 of 0 | <ea> |
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": 2013,
"vin": [ {
"gen": {
"height": 1953
}
}
],
"vout": [ {
"amount": 35056231419049,
"target": {
"tagged_key": {
"key": "1b8a6350d966d7bead3440c85717f4ea21ae23477e0e51b357a0e6f6806cbb0d",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 201, 246, 212, 224, 136, 116, 83, 104, 102, 44, 157, 101, 216, 241, 161, 202, 173, 68, 51, 161, 138, 127, 73, 222, 84, 231, 36, 14, 251, 95, 13, 194, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}