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: a0c2b0bb51d1d5028de32a18cc8b2873be22cc6e4f32cb04c498ab3d7bfef079
Tx prefix hash: a5cd20f33c55bb3ced368cb7557e4da8c877b40ab323674861fca040f9368673
Tx public key: 0150f98d5a09974dc569bcbb37a6132dd0473ec8f1ab0c33127d5473100a3c0c
| Timestamp: 1780068703 | Timestamp [UTC]: 2026-05-29 15:31:43 | Age [y:d:h:m:s]: 00:018:16:50:36 |
| Block: 4622 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4123 | RingCT/type: yes/0 |
| Extra: 010150f98d5a09974dc569bcbb37a6132dd0473ec8f1ab0c33127d5473100a3c0c02090000000c26697be300 | ||
1 output(s) for total of 34.875624362003 HMNY
| stealth address | amount | amount idx | tag |
| 00: 38302c40d4a7a6bfdf5a2352e6b63c98459638fa739904ca8ac00e5942654476 | 34.875624362003 | 5803 of 0 | <b4> |
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": 4682,
"vin": [ {
"gen": {
"height": 4622
}
}
],
"vout": [ {
"amount": 34875624362003,
"target": {
"tagged_key": {
"key": "38302c40d4a7a6bfdf5a2352e6b63c98459638fa739904ca8ac00e5942654476",
"view_tag": "b4"
}
}
}
],
"extra": [ 1, 1, 80, 249, 141, 90, 9, 151, 77, 197, 105, 188, 187, 55, 166, 19, 45, 208, 71, 62, 200, 241, 171, 12, 51, 18, 125, 84, 115, 16, 10, 60, 12, 2, 9, 0, 0, 0, 12, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}