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: a2eb293dcc724b48d05a816e252ffb78ccd2b79da5f39df5404c5deb88646a6e
Tx prefix hash: ee8ad94f2afec26c4657fc153c0c34183d424e67e14974d4374dd0de682be279
Tx public key: dcf3a1a45327526b9d7d7288f115023675eb9072cdc088977e8d8ed7d31bc3bf
| Timestamp: 1780828609 | Timestamp [UTC]: 2026-06-07 10:36:49 | Age [y:d:h:m:s]: 00:002:06:32:14 |
| Block: 7304 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1429 | RingCT/type: yes/0 |
| Extra: 01dcf3a1a45327526b9d7d7288f115023675eb9072cdc088977e8d8ed7d31bc3bf020900000002e49593ff00 | ||
1 output(s) for total of 34.697673164372 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9ea142ee92a35809e0cc71bf6f52224d86af2337a7fb5ca9b067ddf6c66ba06b | 34.697673164372 | 8992 of 0 | <a3> |
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": 7364,
"vin": [ {
"gen": {
"height": 7304
}
}
],
"vout": [ {
"amount": 34697673164372,
"target": {
"tagged_key": {
"key": "9ea142ee92a35809e0cc71bf6f52224d86af2337a7fb5ca9b067ddf6c66ba06b",
"view_tag": "a3"
}
}
}
],
"extra": [ 1, 220, 243, 161, 164, 83, 39, 82, 107, 157, 125, 114, 136, 241, 21, 2, 54, 117, 235, 144, 114, 205, 192, 136, 151, 126, 141, 142, 215, 211, 27, 195, 191, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}