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: 5bd09a52c4454b0f8330dfa72e89440266f0379ebd69b4bf21d59cb3b4fef7fd
Tx prefix hash: b135bf80b9eb6f98b87158fb6a63d1c73443e680e013cbeec793de3a151a6d5f
Tx public key: dcb876edea3b58d573e051c4e168236a06521d45e14134d59cbabf5764927ff5
| Timestamp: 1780061821 | Timestamp [UTC]: 2026-05-29 13:37:01 | Age [y:d:h:m:s]: 00:010:11:58:56 |
| Block: 4530 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3356 | RingCT/type: yes/0 |
| Extra: 01dcb876edea3b58d573e051c4e168236a06521d45e14134d59cbabf5764927ff502090000000126697be300 | ||
1 output(s) for total of 34.881744742464 HMNY
| stealth address | amount | amount idx | tag |
| 00: b5b97474b756d8658777d54f556f733ccbe6bcee0eb125c28b4f9498de232d37 | 34.881744742464 | 5681 of 0 | <64> |
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": 4590,
"vin": [ {
"gen": {
"height": 4530
}
}
],
"vout": [ {
"amount": 34881744742464,
"target": {
"tagged_key": {
"key": "b5b97474b756d8658777d54f556f733ccbe6bcee0eb125c28b4f9498de232d37",
"view_tag": "64"
}
}
}
],
"extra": [ 1, 220, 184, 118, 237, 234, 59, 88, 213, 115, 224, 81, 196, 225, 104, 35, 106, 6, 82, 29, 69, 225, 65, 52, 213, 156, 186, 191, 87, 100, 146, 127, 245, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}