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: 8f5eeb22f1af9fd6e7ec2eb227bba317e57d0b54f287671ca7f8c2575ac75955
Tx prefix hash: 27e9bc96b034c38b231cfa9bf406a813abb7fb77c903a0208570e3060458dc9a
Tx public key: 6c8155c84590d4d8bb7ef03c710c20b708df0373edc59c73033c60c0f5273da9
| Timestamp: 1780689960 | Timestamp [UTC]: 2026-06-05 20:06:00 | Age [y:d:h:m:s]: 00:003:04:40:47 |
| Block: 5629 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2257 | RingCT/type: yes/0 |
| Extra: 016c8155c84590d4d8bb7ef03c710c20b708df0373edc59c73033c60c0f5273da9020900000002e49593ff00 | ||
1 output(s) for total of 34.808702972448 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5664f7fe407147c01973c1a3550aa71a4d98c91d5c14c443d733ad8d17027638 | 34.808702972448 | 7076 of 0 | <5c> |
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": 5689,
"vin": [ {
"gen": {
"height": 5629
}
}
],
"vout": [ {
"amount": 34808702972448,
"target": {
"tagged_key": {
"key": "5664f7fe407147c01973c1a3550aa71a4d98c91d5c14c443d733ad8d17027638",
"view_tag": "5c"
}
}
}
],
"extra": [ 1, 108, 129, 85, 200, 69, 144, 212, 216, 187, 126, 240, 60, 113, 12, 32, 183, 8, 223, 3, 115, 237, 197, 156, 115, 3, 60, 96, 192, 245, 39, 61, 169, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}