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: 6e102293eb1b1218cb145c30eec33a810d26383e5b168ec6339efaa6cf203d5f
Tx prefix hash: 6e940bf871e7a98b245400ed727ee1370b8e339be3d2c5946dd27fda93db4165
Tx public key: 6d279acafbb7bb2cc1e752116f05472e2b5dce52d76f3c399302df65e8d4e46c
| Timestamp: 1780722150 | Timestamp [UTC]: 2026-06-06 05:02:30 | Age [y:d:h:m:s]: 00:002:21:47:18 |
| Block: 6255 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1645 | RingCT/type: yes/0 |
| Extra: 016d279acafbb7bb2cc1e752116f05472e2b5dce52d76f3c399302df65e8d4e46c020900000002e49593ff00 | ||
1 output(s) for total of 34.767166135419 HMNY
| stealth address | amount | amount idx | tag |
| 00: b7b9c7f2957fa89456b18c25306c3aacc0abca3f17edac7f9015f1a2f853a861 | 34.767166135419 | 7736 of 0 | <da> |
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": 6315,
"vin": [ {
"gen": {
"height": 6255
}
}
],
"vout": [ {
"amount": 34767166135419,
"target": {
"tagged_key": {
"key": "b7b9c7f2957fa89456b18c25306c3aacc0abca3f17edac7f9015f1a2f853a861",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 109, 39, 154, 202, 251, 183, 187, 44, 193, 231, 82, 17, 111, 5, 71, 46, 43, 93, 206, 82, 215, 111, 60, 57, 147, 2, 223, 101, 232, 212, 228, 108, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}